Uh oh!
There was an error while loading. Please reload this page.
Fix static_mut_refs lint check logic - #159168
Merged
Merged
Conversation
rustbot
commented
Jul 12, 2026
Collaborator
|
| | ^^^^^^^^^ mutable reference to mutable static | ||
| | | ||
| = note: mutable references to mutable statics are dangerous; it's undefined behavior if any other pointer to the static is used or if any other reference is created for the static while the mutable reference lives | ||
| = help: use a type that relies on "interior mutability" instead; to read more on this, visit <https://doc.rust-lang.org/reference/interior-mutability.html> |
Member
There was a problem hiding this comment.
I don't think this is the suggestion we want to give here -- certainly not the only one. In many cases, using raw pointers is an equally viable solution.
ContributorAuthor
There was a problem hiding this comment.
In the subdiagnostic part it also suggests user to rewrite &mut to &raw mut for using raw pointers, so I think we provide 2 solutions here.
Member
There was a problem hiding this comment.
That just means we're sending mixed signals, where we're saying both "do A" and "do B".
ContributorAuthor
There was a problem hiding this comment.
Understood. Then it would be appropriate to remove that suggestion for explicit referencing (&a or &mut a) cases like this.
RalfJung
commented
Jul 12, 2026
Member
Previously, the lint might suggested using interior mutable type even if it the compiler already decides that the referenced type is interior mutable, while it didn't give such suggestion when the referenced type is considered non-interior mutable. This commit refined the logic as follow: if the referenced type is not interior mutable, then suggests using types with interior mutability; otherwise, suggests removing `mut` if the reference is a *shared* reference. Note that in the latter case, compiler might be silent if the span of the `static mut` definition is not appropriate for suggestions (e.g., comes from macro expansion).
For cases like `&a` or `&mut a`, we only leave a subdiagnostic to suggest user to use raw borrow operators. Using raw pointers in such cases are also equally viable solution but it's not appropriate to suggest using interior mutable types at the same time.
rustbot
commented
Jul 12, 2026
Collaborator
This PR was rebased onto a different main commit. Here's a range-diff highlighting what actually changed. Rebasing is a normal part of keeping PRs up to date, so no action is needed—this note is just to help reviewers. |
estebank
commented
Jul 14, 2026
Contributor
@bors r+ |
Contributor
rust-borsBot
pushed a commit
that referenced
this pull request
Jul 15, 2026
Rollup of 15 pull requests Successful merges: - #159311 (Add 1.97.1 release notes) - #156220 (Implement `VecDeque::truncate_to_range`) - #158608 (Implement `#[diagnostic::opaque]` attribute to hide backtraces of macros.) - #159168 (Fix static_mut_refs lint check logic) - #159242 (resolve: Inherit eager invocation parents) - #159256 (Account for async closures when pointing at lifetime in return type) - #159310 (cleanup: upstream dropped AMX-TF32) - #158348 (Add documentation for the `inline` attribute) - #159181 (add rustc_no_writable to mem::forget and structs it uses) - #159191 (Mark `PrivateItems` with `std_internals` unstable feature.) - #159194 (rustdoc: Fix auto trait normalization env) - #159196 (OnceCell: Improve wording in module docs) - #159289 (Fix Zulip backport command suggestion) - #159294 (renovate: don't update PRs in the merge queue) - #159305 (std: clarify available_parallelism docs for Windows 11 processor groups)
Uh oh!
There was an error while loading. Please reload this page.
rust-timer added a commit
that referenced
this pull request
Jul 15, 2026
Rollup merge of #159168 - cclfmht:fix/issue-158735, r=estebank Fix static_mut_refs lint check logic This PR fixes issue #158735. Previously, the lint might suggested using interior mutable type even if it the compiler already decides that the referenced type is interior mutable, while it didn't give such suggestion when the referenced type is considered non-interior mutable. This commit refined the logic as follow: if the referenced type is not interior mutable, then suggests using types with interior mutability; otherwise, suggests removing `mut` if the reference is a *shared* reference. Note that in the latter case, compiler might be silent if the span of the `static mut` definition is not appropriate for suggestions (e.g., comes from macro expansion). r? @RalfJung
pullBot
pushed a commit
to LeeeeeeM/miri
that referenced
this pull request
Jul 16, 2026
Rollup of 15 pull requests Successful merges: - rust-lang/rust#159311 (Add 1.97.1 release notes) - rust-lang/rust#156220 (Implement `VecDeque::truncate_to_range`) - rust-lang/rust#158608 (Implement `#[diagnostic::opaque]` attribute to hide backtraces of macros.) - rust-lang/rust#159168 (Fix static_mut_refs lint check logic) - rust-lang/rust#159242 (resolve: Inherit eager invocation parents) - rust-lang/rust#159256 (Account for async closures when pointing at lifetime in return type) - rust-lang/rust#159310 (cleanup: upstream dropped AMX-TF32) - rust-lang/rust#158348 (Add documentation for the `inline` attribute) - rust-lang/rust#159181 (add rustc_no_writable to mem::forget and structs it uses) - rust-lang/rust#159191 (Mark `PrivateItems` with `std_internals` unstable feature.) - rust-lang/rust#159194 (rustdoc: Fix auto trait normalization env) - rust-lang/rust#159196 (OnceCell: Improve wording in module docs) - rust-lang/rust#159289 (Fix Zulip backport command suggestion) - rust-lang/rust#159294 (renovate: don't update PRs in the merge queue) - rust-lang/rust#159305 (std: clarify available_parallelism docs for Windows 11 processor groups)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR fixes issue #158735.
Previously, the lint might suggested using interior mutable type even if it the compiler already decides that the referenced type is interior mutable, while it didn't give such suggestion when the referenced type is considered non-interior mutable. This commit refined the logic as follow: if the referenced type is not interior mutable, then suggests using types with interior mutability; otherwise, suggests removing
mutif the reference is a shared reference. Note that in the latter case, compiler might be silent if the span of thestatic mutdefinition is not appropriate for suggestions (e.g., comes from macro expansion).r? @RalfJung