Repository navigation
Disallow ambiguous attributes on expressions (take 2) #160235
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
Open
petrochenkov
wants to merge
1
commit into
rust-lang:main
Choose a base branch
from
petrochenkov:ambattr2
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+382
−23
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,56 @@ | ||
| Regarding https://github.com/rust-lang/rust/pull/159581#issuecomment-5095419394. | ||
|
|
||
| ### Suspicious contexts (single -> list) | ||
|
|
||
| In all these cases if `$expr` has a top level attribute inside it, it will migrate from a single to list context if the parentheses from the macro variable are not correctly preserved in AST. | ||
|
|
||
| ```rust | ||
| // method call arguments | ||
| r.method($expr, ...) | ||
|
|
||
| // array element or size | ||
| [$expr, 11, 12] | ||
|
|
||
| // function call argument | ||
| func($expr, 11, 12) | ||
|
|
||
| // tuple element | ||
| ($expr, 11, 12) | ||
|
|
||
| // const generic arguments (if supported at all) | ||
| foo::<$expr>() | ||
| ``` | ||
|
|
||
| ### Suspicious contexts (expr -> stmt) | ||
|
|
||
| In all these cases if `$expr` has a top level attribute inside it, it will migrate from a single expression to statement context if the parentheses from the macro variable are not correctly preserved in AST. | ||
|
|
||
| ```rust | ||
| // $expr is: | ||
|
|
||
| // postfix await, yield or use | ||
| #[attr] val.await | ||
| #[attr] val.yield | ||
| #[attr] val.use | ||
|
|
||
| // field or method access | ||
| #[attr] val.field | ||
| #[attr] val.method() | ||
|
|
||
| // function call or indexing | ||
| #[attr] val() | ||
| #[attr] val[] | ||
|
|
||
| // expression | ||
| #[attr] val? | ||
|
|
||
| // path | ||
| #[attr] path | ||
| ``` | ||
|
|
||
| If an attribute starts a statement as a part of some larger expression (e.g. a binary operator), it will already be reported as an error by https://github.com/rust-lang/rust/pull/160235#issuecomment-5159173426. | ||
|
|
||
| ### Conclusion | ||
|
|
||
| These examples are only ambiguous if any of the involved attributes are active (including `cfg`), except that `cfg_attr` is ok (because we know what it does, and it does not depend on context). | ||
| So we don't need to gate any of this during parsing, and can continue using expansion-time gating. |
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.
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.
I'm sure you're aware but ideally we wouldn't emit two feature gate errors (parse-time & expansion-time) for code that survives macro expansion.
Maybe just make both diagnostics have the same message & diagnostic duplication will do the rest.
View changes since the review
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.
Yes, I also wanted to deduplicate them in the final version.