-
Notifications
You must be signed in to change notification settings - Fork 13.3k
Do not accidentally treat multi-segment meta-items as single-segment #58899
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Conversation
r? @eddyb (rust_highfive has picked a reviewer for you, use r? to override) |
@bors try |
⌛ Trying commit f922e0d with merge 290ac7b29f41ff9fa5232f9a1116ea71a3501063... |
☀️ Try build successful - checks-travis |
@craterbot run start=master#c0086b9e8972fef9fd4af24bae20d45021ed06c6 end=try#290ac7b29f41ff9fa5232f9a1116ea71a3501063 mode=check-only |
👌 Experiment ℹ️ Crater is a tool to run experiments across parts of the Rust ecosystem. Learn more |
🚧 Experiment ℹ️ Crater is a tool to run experiments across parts of the Rust ecosystem. Learn more |
🚨 Experiment 🆘 Can someone from the infra team check in on this? @rust-lang/infra |
@craterbot retry |
🛠️ Experiment ℹ️ Crater is a tool to run experiments across parts of the Rust ecosystem. Learn more |
🚧 Experiment ℹ️ Crater is a tool to run experiments across parts of the Rust ecosystem. Learn more |
🚨 Experiment 🆘 Can someone from the infra team check in on this? @rust-lang/infra |
@craterbot retry |
🛠️ Experiment ℹ️ Crater is a tool to run experiments across parts of the Rust ecosystem. Learn more |
🚧 Experiment ℹ️ Crater is a tool to run experiments across parts of the Rust ecosystem. Learn more |
🎉 Experiment
|
Oh, great, no regressions. |
I'm going to beta-nominate the first three commits (https://github.com/rust-lang/rust/pull/58899/files/cd71788b8cbc55eb89a391eb65bcc6cb27c5a107) despite the size. |
Remove methods `Attribute::span` and `MetaItem::span` duplicating public fields
@bors r=estebank |
📌 Commit 2fd4cbb has been approved by |
Do not accidentally treat multi-segment meta-items as single-segment Fixes #55168 and many other regressions from #50030 Basically, attributes like `#[any::prefix::foo]` were commonly interpreted as `#[foo]` due to `name()` successfully returning the last segment (this applies to nested things as well `#[attr(any::prefix::foo)]`).
☀️ Test successful - checks-travis, status-appveyor |
Backport candidate prepared in #59259 |
Rustup Supersedes #3889 Addresses some review comments from previous PR and rustups to rust-lang/rust#58899
Rustup Supersedes #3889 Addresses some review comments from previous PR and rustups to rust-lang/rust#58899
Rustup Supersedes #3889 Addresses some review comments from previous PR and rustups to rust-lang/rust#58899
Rustup Supersedes #3889 Addresses some review comments from previous PR and rustups to rust-lang/rust#58899
Rustup Supersedes #3889 Addresses some review comments from previous PR and rustups to rust-lang/rust#58899
Turns out, this was never supposed to be supported in the first place. - rust-lang/rust#58899
Turns out, this was never supposed to be supported in the first place. - rust-lang/rust#58899
[beta] Do not accidentally treat multi-segment meta-items as single-segment Partial backport of #58899 to beta
Fixes #55168 and many other regressions from #50030
Basically, attributes like
#[any::prefix::foo]
were commonly interpreted as#[foo]
due toname()
successfully returning the last segment (this applies to nested things as well#[attr(any::prefix::foo)]
).