-
Notifications
You must be signed in to change notification settings - Fork 12.7k
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
Change leak check and suspicious auto trait lint warning messages #120716
Conversation
I think the "a future release" wording from the original (vs ambiguous "the future") is valuable. Perhaps even go further, "a future Rust release"? |
Yes, what you suggest seems also good to me. Would leave a decision up to @lcnr when they do a review. |
☔ The latest upstream changes (presumably #120558) made this pull request unmergeable. Please resolve the merge conflicts. |
dc9d685
to
b306762
Compare
b21d3ce
to
29cd7a2
Compare
This comment has been minimized.
This comment has been minimized.
removing the |
29cd7a2
to
ac045b0
Compare
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 in src/tools/clippy cc @rust-lang/clippy |
This comment has been minimized.
This comment has been minimized.
0f5446e
to
7bab48c
Compare
☔ The latest upstream changes (presumably #120881) made this pull request unmergeable. Please resolve the merge conflicts. |
271485f
to
af7925f
Compare
This comment has been minimized.
This comment has been minimized.
35ea987
to
aaf24d4
Compare
☔ The latest upstream changes (presumably #121034) made this pull request unmergeable. Please resolve the merge conflicts. |
aaf24d4
to
cbbb7b3
Compare
cbbb7b3
to
17e64e1
Compare
/// were previously unsound, quite subtle, and have been recently modified. | ||
/// This change caused the automatic implementation to be disabled in more | ||
/// cases, potentially breaking some code. | ||
pub SUSPICIOUS_AUTO_TRAIT_IMPLS, |
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.
there's a "removed_lints" storage somewhere, the lint should be mentioned there, otherwise the error on allow(suspicious_auto_trait_impls)
is suboptimal, it's done via LintStore::register_removed
.
r=me after updating description and final nit. please also add "closes #93367" |
c1d94dd
to
13575bc
Compare
13575bc
to
4803f17
Compare
@bors r=lcnr |
Rollup of 10 pull requests Successful merges: - rust-lang#120716 (Change leak check and suspicious auto trait lint warning messages) - rust-lang#121195 (unstable-book: Separate testing and production sanitizers) - rust-lang#121205 (Merge `CompilerError::CompilationFailed` and `CompilerError::ICE`.) - rust-lang#121233 (Move the extra directives for `Mode::CoverageRun` into `iter_header`) - rust-lang#121256 (Allow AST and HIR visitors to return `ControlFlow`) - rust-lang#121307 (Drive-by `DUMMY_SP` -> `Span` and fmt changes) - rust-lang#121308 (Add regression test for rust-lang#103369) - rust-lang#121310 (Remove an old hack for rustdoc) - rust-lang#121311 (Make `is_nonoverlapping` `#[inline]`) - rust-lang#121319 (return `ty::Error` when equating `ty::Error`) r? `@ghost` `@rustbot` modify labels: rollup
Rollup merge of rust-lang#120716 - spastorino:change-some-lint-msgs, r=lcnr Change leak check and suspicious auto trait lint warning messages The leak check lint message "this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!" is misleading as some cases may not be phased out and could end being accepted. This is under discussion still. The suspicious auto trait lint the change in behavior already happened, so the new message is probably more accurate. r? `@lcnr` Closes rust-lang#93367
The leak check lint message "this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!" is misleading as some cases may not be phased out and could end being accepted. This is under discussion still.
The suspicious auto trait lint the change in behavior already happened, so the new message is probably more accurate.
r? @lcnr
Closes #93367