-
-
Notifications
You must be signed in to change notification settings - Fork 14.7k
Add gated const item paths support for selected builtin attributes. #154708
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
BarronKane
wants to merge
5
commits into
rust-lang:main
Choose a base branch
from
BarronKane:feature-attr-pad-consts
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.
Open
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
74951ce
rustc_attr_parsing: allow const item paths in selected builtin attrs
BarronKane c214df9
fix: tidy use sorting, rustc version, and issue attribution
BarronKane 4176d12
fix: const-attr-paths need .stderr issue tracking
BarronKane 0a02f2d
fix: const-attr-paths hir pretty printing
BarronKane 59783c3
refactor: more general terminology and use existing attr parse machinery
BarronKane 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
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.
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.
For who does end up reviewing this PR, I'm taking another look at things, and I want to note that in
fn parse_alignment_or_const_path<S: Stage>, I'm returning 1 onShouldEmit::Nothing. This was a deliberate decision becauserepr(packed)itself returns 1 by default elsewhere, and is effectively no-op otherwise, but part of not being obtrusive to the codebase I shimmed it in there in order to avoid a heavier refactor ofrepr.rsto make it typed. Categorically it is fake data, but I think it's defensible from this stance. If the lang and compiler teams want to go this direction of resolutions within attributes, this should be pulled out for a better solution so future work doesn't trip over it. Deferred state should be represented properly, so I wanted to note this now.