-
Notifications
You must be signed in to change notification settings - Fork 762
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
Lex.charset fixes #2768
Lex.charset fixes #2768
Conversation
Instead of "(hexadecimal)", what about |
We're not doing "16" as subscript anywhere else in the standard, as far as I know. Maybe this single location (and in a note) is not a good place to start. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Seems like an improvement.
Oh, and please change the commit comment to use a "[lex.charset]" prefix. |
@zygoloid, I see this issue is marked as needing review from SG16. I'm assuming you're just looking for any comments SG16 participants might have to offer. If you would like something more formal, please let me know. |
@tahonermann: Specifically, since you are chair of SG16, do you feel this change should be reviewed by SG16? If not, could you please review it and comment whether you're ok with the change? |
@jensmaurer @zygoloid, I see no need for this change to be further reviewed by SG16. I have reviewed it and am happy with it. |
Please rebase and fix the conflicts, then force-push. |
Clarify that \U sequences not beginning 00 are ill-formed. Clarify handling of code points naming reserved or noncharacter code points. Remove unnecessary circumlocution through "short identifiers" by directly talking about code points. Use code point values directly rather than using C++ 0x notation. [lex.string] Fix description of what UCNs mean, and convert it to a note.
5acbaf2
to
32511c7
Compare
Fixes #2752.