-
Notifications
You must be signed in to change notification settings - Fork 12.8k
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
Split Diagnostics for Uncommon Codepoints: Add Individual Identifier Types #120840
Split Diagnostics for Uncommon Codepoints: Add Individual Identifier Types #120840
Conversation
@rustbot ready |
☔ The latest upstream changes (presumably #120486) made this pull request unmergeable. Please resolve the merge conflicts. |
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.
Thanks for working on this! Sorry for taking a bit. I have a couple of suggestions.
I'll probably have wording suggestions when I look at this, mostly we shouldn't be mentioning the Not_NFKC or whatever as much as the underlying meaning. I'll help with that when I get a chance hopefully in a few days. If it's taking too long it's ultimately fine to land this if properly reviewed by someone and we can patch those up later. |
2f6e822
to
3bf4164
Compare
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
@rustbot ready |
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.
Thanks! I have two suggestions but apart from that I really like it! However, I'll let Manishearth have the final say :)
edd9cf9
to
9afe7e6
Compare
Comments resolved and commits squashed! |
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.
Good start with the wording, I don't actually think we should mention unicode codepoint, "character" is fine in this context (even though generally in unicode contexts it can be ambiguous).
I've suggested fixes (make sure to fix both the singular and the plural!)
@rustbot ready |
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.
Thanks
@bors r=fmease,Manishearth
Did bors give up? 🤔🤔🤔 |
Ah, I put it in a review comment which it doesn't recognize. @bors r=fmease,Manishearth |
Sorry about that |
dcd5118
to
8bccceb
Compare
Done! |
@rustbot ready |
@bors r=fmease,Manishearth |
…llaumeGomez Rollup of 5 pull requests Successful merges: - rust-lang#120656 (Allow tests to specify a `//@ filecheck-flags:` header) - rust-lang#120840 (Split Diagnostics for Uncommon Codepoints: Add Individual Identifier Types) - rust-lang#121554 (Don't unnecessarily change `SIGPIPE` disposition in `unix_sigpipe` tests) - rust-lang#121590 (Correctly handle if rustdoc JS script hash changed) - rust-lang#121620 (Fix more rust-lang#121208 fallout (round 3)) r? `@ghost` `@rustbot` modify labels: rollup
Rollup merge of rust-lang#120840 - HTGAzureX1212:HTGAzureX1212/unicode-identifier-types, r=fmease,Manishearth Split Diagnostics for Uncommon Codepoints: Add Individual Identifier Types This pull request further modifies the `uncommon_codepoints` lint, adding the individual identifier types of `Technical`, `Not_NFKC`, `Exclusion` and `Limited_Use` to the diagnostic message. Example rendered diagnostic: ``` error: identifier contains a Unicode codepoint that is not used in normalized strings: 'ij' --> $DIR/lint-uncommon-codepoints.rs:6:4 | LL | fn dijkstra() {} | ^^^^^^^ = note: this character is included in the Not_NFKC Unicode general security profile ``` Second step of rust-lang#120228.
This pull request further modifies the
uncommon_codepoints
lint, adding the individual identifier types ofTechnical
,Not_NFKC
,Exclusion
andLimited_Use
to the diagnostic message.Example
After:
Before:
Second step of #120228.