-
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
Fix E0284 to not use incorrect wording #71960
Conversation
r? @davidtwco (rust_highfive has picked a reviewer for you, use r? to override) |
Nominating for backport because the current error can be incredibly misleading and the risk is low, but won't push for it too much as it is not critical. |
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.
@bors r=davidtwco |
📌 Commit a7b03ad has been approved by |
Rollup of 5 pull requests Successful merges: - rust-lang#70733 (Add Arc::{incr,decr}_strong_count) - rust-lang#71598 (improve Drop documentation) - rust-lang#71783 (Detect errors caused by `async` block in 2015 edition) - rust-lang#71903 (reword "possible candidate" import suggestion) - rust-lang#71960 (Fix E0284 to not use incorrect wording) Failed merges: r? @ghost
Adding |
unilaterally accepting for beta-backport. |
[beta] Rollup backports This includes: * Fail if I/O error occurs during testing rust-lang#72089 * Fix hang in lexical_region_resolve rust-lang#72087 * Fix E0284 to not use incorrect wording rust-lang#71960 * Bump pulldown-cmark rust-lang#71682
Fix #71584, fix #69683.