-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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
Cleanup error handlers #118470
Cleanup error handlers #118470
Conversation
Some changes occurred in src/tools/clippy cc @rust-lang/clippy Some changes might have occurred in exhaustiveness checking cc @Nadrieril rust-analyzer is developed in its own repository. If possible, consider making this change to rust-lang/rust-analyzer instead. cc @rust-lang/rust-analyzer Some changes occurred to the CTFE / Miri engine cc @rust-lang/miri Some changes occurred to the CTFE / Miri engine cc @rust-lang/miri The Miri subtree was changed cc @rust-lang/miri Some changes occurred to MIR optimizations cc @rust-lang/wg-mir-opt Some changes occurred to the core trait solver cc @rust-lang/initiative-trait-system-refactor Some changes occurred in cc @BoxyUwU |
@@ -110,7 +110,7 @@ struct LayoutCx<'a> { | |||
impl<'a> LayoutCalculator for LayoutCx<'a> { | |||
type TargetDataLayoutRef = &'a TargetDataLayout; | |||
|
|||
fn delay_bug(&self, txt: String) { | |||
fn delayed_bug(&self, txt: String) { |
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.
CC @Veykril this will be fun to handle.
EDIT: for context, when RA is built outside of rust-lang/rust, it uses a version ra_ap_rustc_abi
from crates.io that gets published every Tuesday. So no need to do anything @nnethercote, we just have to be a little careful.
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.
That particular commit isn't that important, so if it's a pain I can just remove it.
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.
No, don't worry about it.
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.
Isn't that only a problem when we do a sync while the changes haven't been pushed to crates io yet? fwiw we can change the autopublish time to be right before your usual sync times if you want
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.
It is, but it's easy to patch when syncing back, then undo that when we upgrade to the published version.
Some changes occurred in need_type_info.rs cc @lcnr |
I added a few more commits. I'll stop now, I promise :) |
It has a single call site.
`ErrorGuaranteed` should be used for all error methods involving the `Error` level, e.g. as is done for the corresponding `span_err` methods.
Because `span_note_diag` doesn't follow the naming structure used for the error reporting functions.
To match the `FailureNote` variant of `Level`.
Because the variant name in `Level` is `Note`, and the `without_error` suffix is omitted in similar cases like `struct_allow` and `struct_help`.
…bug`. Because the corresponding `Level` is `DelayedBug` and `span_delayed_bug` follows the pattern used everywhere else: `span_err`, `span_warning`, etc.
…ed_bugs`. For reasons similar to the previous commit.
…bug`. In line with the previous commits.
To match with the previous commits.
- Avoid unnecessary `inner` local variables. - Use `borrow_mut` everywhere (instead of the synonym `lock`).
It has a single call site.
40d6f9f
to
61f9356
Compare
I added the requested comment. |
@bors r=compiler-errors |
☀️ Test successful - checks-actions |
Finished benchmarking commit (2da59b8): comparison URL. Overall result: no relevant changes - no action needed@rustbot label: -perf-regression Instruction countThis benchmark run did not return any relevant results for this metric. 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.
CyclesThis benchmark run did not return any relevant results for this metric. Binary sizeThis benchmark run did not return any relevant results for this metric. Bootstrap: 672.083s -> 671.012s (-0.16%) |
…-2, r=compiler-errors Cleanup error handlers some more A sequel to rust-lang#118470. r? `@compiler-errors`
…-2, r=compiler-errors Cleanup error handlers some more A sequel to rust-lang#118470. r? ``@compiler-errors``
…-2, r=compiler-errors Cleanup error handlers some more A sequel to rust-lang#118470. r? ```@compiler-errors```
Rollup merge of rust-lang#118587 - nnethercote:cleanup-error-handlers-2, r=compiler-errors Cleanup error handlers some more A sequel to rust-lang#118470. r? ```@compiler-errors```
…r=compiler-errors Cleanup error handlers Mostly by making function naming more consistent. More to do after this, but this is enough for one PR. r? compiler-errors
Mostly by making function naming more consistent. More to do after this, but this is enough for one PR.
r? compiler-errors