Can NFKC turn valid UAX 31 identifiers into non-identifiers?

Hi,

The Rust community is considering
<https://github.com/rust-lang/rfcs/pull/2457> adding non-ascii identifiers,
which follow UAX #31 <http://www.unicode.org/reports/tr31/> (XID_Start
XID_Continue*, with tweaks). The proposal also asks for identifiers to be
treated as equivalent under NFKC.

Are there any cases where this will lead to inconsistencies? I.e. can the
NFKC of a valid UAX 31 ident be invalid UAX 31?

(In general, are there other problems folks see with this proposal?)

Thanks,
-Manish
Received on Mon Jun 04 2018 - 14:50:02 CDT