Don't assume traits used as type are trait objs in 2021 edition - #131239
Conversation
|
Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @lcnr (or someone else) some time within the next two weeks. Please see the contribution instructions for more information. Namely, in order to ensure the minimum review times lag, PR authors and assigned reviewers should ensure that the review label (
|
|
HIR ty lowering was modified cc @fmease |
|
@rustbot author |
FYI the word "vunlnerability" has a specific meaning (i.e. a weakness that makes something easy to be attacked/exploited) in the context of this repo (e.g. related to compiler or std), but this PR is just trying to improve diagnostics not trying to address an exploit. |
|
I see vulnerability as when something is not right and I fix it. Ok I will change the word |
|
We usually call those those "bugs" or "diagnostic issues", "vulnerability" usually indicates an exploitable weakness that has to do with security that wg-security-response would need to look at. |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
4481349 to
6a66761
Compare
|
@rustbot review |
71f96e3 to
6037e9e
Compare
This comment has been minimized.
This comment has been minimized.
a28d963 to
60f3737
Compare
|
r=me after CI |
60f3737 to
16fe4ce
Compare
|
☔ The latest upstream changes (presumably #131511) made this pull request unmergeable. Please resolve the merge conflicts. |
16fe4ce to
9a2772e
Compare
|
@bors r+ rollup |
Fixes #127548
When you use a trait as a type, the compiler automatically assumes you meant to use a trait object, which is not always the case.
This PR fixes the bug where you don't need a trait object, so the error message was changed to:
Also fixes some ICEs:
Fixes #120241
Fixes #120482
Fixes #125512