-
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
Always print '_, even for erased lifetimes. #102068
Conversation
r? @eholk (rust-highfive has picked a reviewer for you, use r? to override) |
@bors r+ |
Ah, looks like a few more tests still need blessed, but you can r=me after they're passing. |
This comment has been minimized.
This comment has been minimized.
20da4f0
to
eee64a0
Compare
@bors r=eholk |
…eholk Always print '_, even for erased lifetimes. Explicit lifetime arguments are now the recommended syntax in rust 2018 and rust 2021. This PR applies this discipline to rustc itself.
@bors r- |
failed in rollup |
Some changes occurred in src/tools/clippy cc @rust-lang/clippy |
@bors r=eholk |
I wonder if this if this is true in the |
@@ -38,10 +38,10 @@ | |||
StorageLive(_4); // scope 0 at $DIR/funky_arms.rs:+4:9: +4:19 | |||
StorageLive(_5); // scope 0 at $DIR/funky_arms.rs:+4:22: +4:37 | |||
_5 = &(*_1); // scope 0 at $DIR/funky_arms.rs:+4:22: +4:37 | |||
_4 = Formatter::sign_plus(move _5) -> bb1; // scope 0 at $DIR/funky_arms.rs:+4:22: +4:37 | |||
_4 = Formatter::<'_>::sign_plus(move _5) -> bb1; // scope 0 at $DIR/funky_arms.rs:+4:22: +4:37 |
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.
ah, see this one! I don't think Formatter::<'_>::sign_plus
is more prefereable to Formatter::sign_plus
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 don't think this is an issue. Diagnostics only use this in TypeNs
position, so that's good. MIR dump is an internal debugging tool, so having non-beginner-friendly printing should be ok.
…eholk Always print '_, even for erased lifetimes. Explicit lifetime arguments are now the recommended syntax in rust 2018 and rust 2021. This PR applies this discipline to rustc itself.
It just needs the src/tools/miri test to be updated:
|
I think you just need to run |
@saethlin How do I run |
That would probably be a question for @oli-obk, I've never operated the Miri tests from |
I don't think we have those docs yet, where should they usually go? |
e01a3bd
to
eb1ddd2
Compare
The Miri subtree was changed cc @rust-lang/miri |
@bors r=eholk rollup=iffy |
☀️ Test successful - checks-actions |
Finished benchmarking commit (e1c28e0): comparison URL. Overall result: ✅ improvements - no action needed@rustbot label: -perf-regression Instruction countThis is a highly reliable metric that was used to determine the overall result at the top of this comment.
Max RSS (memory usage)ResultsThis is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
CyclesResultsThis is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
Footnotes |
Always print '_, even for erased lifetimes. Explicit lifetime arguments are now the recommended syntax in rust 2018 and rust 2021. This PR applies this discipline to rustc itself.
Always print '_, even for erased lifetimes. Explicit lifetime arguments are now the recommended syntax in rust 2018 and rust 2021. This PR applies this discipline to rustc itself.
Always print '_, even for erased lifetimes. Explicit lifetime arguments are now the recommended syntax in rust 2018 and rust 2021. This PR applies this discipline to rustc itself.
Explicit lifetime arguments are now the recommended syntax in rust 2018 and rust 2021. This PR applies this discipline to rustc itself.