5 ms·
Maybe you are referring the reference [1], which indeed mentions NFKC. As far as I know there is no consensus of the normalization form [2] and the current impl
by lifthrasiir 13y ago
Maybe you are referring the reference [1], which indeed mentions NFKC. As far as I know there is no consensus of the normalization form [2] and the current implementation is not guaranteed to stay, which is why Unicode identifiers are gated behind a `#[feature]` flag.
[1] http://static.rust-lang.org/doc/0.9/rust.html#input-format http://static.rust-lang.org/doc/0.9/rust.html#input-format
[2] https://github.com/mozilla/rust/issues/2253 https://github.com/mozilla/rust/issues/2253
- dbaupp 13y ago(Also, as that bug suggests, we don't actually do any normalisation at all yet.)
- vorg 13y agoYes, I started reading the reference. The normalization form issue is different to the #[non_ascii_idents] feature, though. The issue 2253 does mention address it, but all the comments mention the issue of NFC/NFKC normalization specifically for filesystem lookup and for program identifiers, but not for the lexing stage. That issue is obviously the best place to continue any conversation about it.