-
Notifications
You must be signed in to change notification settings - Fork 12.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Move lexer punctuation confusables list to unicode-security
crate and sync it with newest Unicode version.
#70002
Comments
cc @estebank @rust-lang/wg-diagnostics re:confusables list |
It's a bit tough because that list isn't automatically generated, or it has been at a point in the past but since then it has been manually edited and changed. Those amendments are valuable and should not be lost by an automatic regeneration. One could think about having two lists though, one automatically generated, the other with the rust-specific edits/improvements. |
As i've recently got a crate that has |
The former two lists are here. Also cc @Manishearth to see whether the second list is of some value to further development of UTS39. |
The in-tree list is specifically about things which are confusable with rust syntax |
Yes, and rust syntax here means most of ASCII punctuation characters. I saw one major difference between this list and the UTS39 one is that most of the items here are just unintentional, and not for security reasons. For example,
I'm using an IME daily, and a single shift key press toggles between Latin mode and Han mode, where the comma key corresponds to these two characters in each mode. And it's really easy to unintentionally get them wrong. So while this item is not in UTS39 list, it is practically quite useful. |
unicode-security
crate.
unicode-security
crate.unicode-security
crate and sync it with newest Unicode version.
Updated the issue title to reflect the actual discussion topic here - the libs part is already done in #69929. |
Now that Unicode 13 is released, maybe we should bump the unicode version.
The text was updated successfully, but these errors were encountered: