-
Notifications
You must be signed in to change notification settings - Fork 13.4k
Improve lifetime errors with implicit trait object lifetimes #66679
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
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.
This appears to apply to more than just trait objects.
r=me with comments addressed.
src/librustc_mir/borrow_check/nll/region_infer/error_reporting/region_name.rs
Outdated
Show resolved
Hide resolved
src/librustc_mir/borrow_check/nll/region_infer/error_reporting/region_name.rs
Outdated
Show resolved
Hide resolved
@bors r+ |
📌 Commit 8f4d3632b03d8526f643c9ccab99172f02a83a07 has been approved by |
☔ The latest upstream changes (presumably #66824) made this pull request unmergeable. Please resolve the merge conflicts. |
8f4d363
to
415dce1
Compare
Rebased, but need to rerun tests and bless... |
The job Click to expand the log.
I'm a bot! I can only do what humans tell me to, so if this was not helpful or you have suggestions for improvements, please ping or otherwise contact |
415dce1
to
2a86b6c
Compare
@matthewjasper I think this is ready now :) |
@bors r+ |
📌 Commit 2a86b6c has been approved by |
🌲 The tree is currently closed for pull requests below priority 1000, this pull request will be tested once the tree is reopened |
…r=matthewjasper Improve lifetime errors with implicit trait object lifetimes r? @matthewjasper cc @estebank I still think the ideal solution would be to construct a `BrAnon`, but that seems like a more invasive change, and can be done later. This at least gets rid of the hack in `OutliveSuggestion` and is slightly more principled.
Rollup of 9 pull requests Successful merges: - #66503 (More useful test error messages on should_panic(expected=...) mismatch) - #66662 (Miri: run panic-catching tests in liballoc) - #66679 (Improve lifetime errors with implicit trait object lifetimes) - #66726 (Use recursion_limit for const eval stack limit) - #66790 (Do `min_const_fn` checks for `SetDiscriminant`s target) - #66832 (const_prop: detect and avoid catching Miri errors that require allocation) - #66880 (Add long error code explanation message for E0203) - #66890 (Format liballoc with rustfmt) - #66896 (pass Queries to compiler callbacks) Failed merges: r? @ghost
r? @matthewjasper
cc @estebank
I still think the ideal solution would be to construct a
BrAnon
, but that seems like a more invasive change, and can be done later. This at least gets rid of the hack inOutliveSuggestion
and is slightly more principled.