-
Notifications
You must be signed in to change notification settings - Fork 13.5k
Port #[used]
to new attribute parsing infrastructure
#142818
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
base: master
Are you sure you want to change the base?
Conversation
|
Some changes occurred in compiler/rustc_attr_parsing Some changes occurred in compiler/rustc_codegen_ssa Some changes occurred in compiler/rustc_codegen_ssa/src/codegen_attrs.rs Some changes occurred in compiler/rustc_attr_data_structures Some changes occurred in compiler/rustc_passes/src/check_attr.rs |
44fa5f0
to
073e2c6
Compare
073e2c6
to
468dd68
Compare
@rustbot author |
Reminder, once the PR becomes ready for a review, use |
☔ The latest upstream changes (presumably #142826) made this pull request unmergeable. Please resolve the merge conflicts. |
468dd68
to
674be35
Compare
@rustbot ready |
e70cbef
to
30d851d
Compare
Rebased to solve merge conflicts |
☔ The latest upstream changes (presumably #142878) made this pull request unmergeable. Please resolve the merge conflicts. |
be02b70
to
0031aab
Compare
just to be clear @JonathanBrouwer, is the behavior right now exactly the same as before with regards to errors and which attribute applies in case of duplicates or not? |
@jdonszelmann When multiple different attributes are applied the behaviour has changed. This is fine because What has changed:
Before: Error, "compiler and linker can't be used together". This is a wrong error since
Before: No error, ratcheting behaviour so "linker " is used
Before: Error |
0031aab
to
708f45f
Compare
^ Rebased |
I'd say we should keep this an error if it is right now, since if we relax the requirement it's very hard to at some point make it an error again since that'd be a breaking change. Until T-lang decided on #142836 I'm not entirely comfortable with removing the error |
@jdonszelmann Would you want to keep all behaviour exactly as it was before? I think the old behaviour is really weird, we should either always ratchet or always error with different attrs (which is still my preference) ideally. I'm happy to implement the old behaviour if you really want though :) |
ah right, fair enough |
ok then I would approve but I'm suspending all attribute PRs for a little bit until #142777 goes through (see #t-compiler > attribute parsing rework @ 💬 |
Sounds good, I'll keep an eye on when it gets through and rebase on it :) |
@bors r+ rollup |
Signed-off-by: Jonathan Brouwer <jonathantbrouwer@gmail.com>
708f45f
to
9b3f729
Compare
@jdonszelmann This one was not rebased on the encode-cross-crate PR yet, did that now ^ |
Ah I see |
Whoops |
@bors r+ |
…=jdonszelmann Port `#[used]` to new attribute parsing infrastructure Ports `used` to the new attribute parsing infrastructure for rust-lang#131229 (comment) r? `@jdonszelmann`
@bors r- |
☔ The latest upstream changes (presumably #143074) made this pull request unmergeable. Please resolve the merge conflicts. |
Ports
used
to the new attribute parsing infrastructure for #131229 (comment)r? @jdonszelmann