XID_Start / XID_Continue might not be quite right

[graydon]

http://www.open-std.org/jtc1/sc22/wg14/www/docs/n1518.htm

The ISO JTC1/SC22/WG14 (C language) think that possibly UTR#31 didn't quite hit the nail on the head in terms of defining identifier syntax. They have a couple tweaks in mind. Consider following their lead.

[catamorphism]

Bug triage. Re-nominating to change to milestone 1, well-defined.

[graydon]

accepted for backwards-compatible milestone

[emberian]

Non-ascii identifiers are currently feature gated, so this isn't as pressing, but we still need to figure out what to do here. Re-nominating, I don't think this needs to be backcompat.

[pnkfelix]

Correct, non-ascii idents are feature-gated. Recategorizing as P-low (and not 1.0).

[yongqli]

I would really like to see Unicode superscripts allowed, as subscripts already are. I would be willing to make a pull request to implement this.

[steveklabnik]

Triage: unicode identifiers are still feature gated, no changes.

[rurban]

XID_Start / XID_Continue has one small bug, and is not enough to get proper unicode identifiers safe. See also http://websec.github.io/unicode-security-guide/
You need to add mixed script protections (TR39 Restriction levels), normalize them (to NFC or NFKC_Casefold), and maybe disallow confusables.
A short overview is here: http://perl11.org/blog/unicode-identifiers.html

bug: U+3164 HANGUL FILLER and U+ffa0 are wrongly specified as ID_Continue. Disallow these.

[Centril]

Closing in favor of #55467.

[SimonSapin]

@Centril, is this specific issue actually addressed in rust-lang/rfcs#2457 or tracked in #55467? As far as I can tell they specify unmodified XID_Start and XID_Continue.

[Centril]

@SimonSapin at least tracked in that issue to consolidate; tho I didn't read the issue description in detail.

[SimonSapin]

I’ve added this as a checkbox in Unresolved Questions in #55467