Handle const-checks for &mut outside of HasMutInterior
#66654
Merged
Conversation
This file contains 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
|
(rust_highfive has picked a reviewer for you, use r? to override) |
rust-highfive
added
the
S-waiting-on-review
|
r? @eddyb (although I'd like to work on this a bit more, it's not quite ready) |
ecstatic-morse
changed the title
&mut outside of HasMutInterior&mut outside of HasMutInterior
ecstatic-morse
force-pushed
the
check-consts-ref
branch
from
ba0ce7e
to
b40d0bd
Compare
|
☔ The latest upstream changes (presumably #66640) made this pull request unmergeable. Please resolve the merge conflicts. |
Centril
reviewed
Nov 23, 2019
| fn in_static(_cx: &ConstCx<'_, 'tcx>, _static: &Static<'tcx>) -> bool { | ||
| // FIXME(eddyb) should we do anything here for value properties? | ||
| false | ||
| fn in_static(cx: &ConstCx<'_, 'tcx>, statik: &Static<'tcx>) -> bool { |
There was a problem hiding this comment.
(btw, a doc comment on these methods would be great)
| .as_local() | ||
| .map_or(false, |local| self.derived_from_illegal_borrow.contains(local)); | ||
|
|
||
| // Don't emit errors for borrows of values that are *themselves* the result of |
There was a problem hiding this comment.
Can we delay_span_bug just in case?
eddyb
reviewed
Nov 26, 2019
| // Don't emit errors for borrows of values that are *themselves* the result of | ||
| // an illegal borrow (e.g., the outermost `&` in `&&Cell::new(42)`). We want to | ||
| // point the user to the place where the original illegal borrow occurred, not | ||
| // to subsequent borrows of the resulting value. |
There was a problem hiding this comment.
I thought this was resolved by simply not having any qualifs on &Cell::new(42).
&T is always Freeze + Copy, regardless of T, so no qualif bits need to be set.
The only reason they were before was for promotion, which is why we split promotion into its own check.
There was a problem hiding this comment.
I think you're right. This means I can clean up a lot more!
ecstatic-morse
force-pushed
the
check-consts-ref
branch
2 times, most recently
from
c93bb56
to
639aeec
Compare
|
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 |
|
☔ The latest upstream changes (presumably #66677) made this pull request unmergeable. Please resolve the merge conflicts. |
ecstatic-morse
force-pushed
the
check-consts-ref
branch
from
639aeec
to
4c1f3b1
Compare
Now, `derived_from_illegal_borrow` is also applied to reborrows, so we don't show the user a useless error message.
ecstatic-morse
force-pushed
the
check-consts-ref
branch
from
4c1f3b1
to
7f35ab6
Compare
|
Now that #66640 has been merged, the const-checker treats borrows of a @matthewjasper I'm not quite sure why #66587 didn't cause this test to change. How do I check that |
|
I believe it didn't change in that PR because we don't special case reborrows in |
|
The |
This error code is never emitted, and the contents of this test are identical to that of `E0017.rs`.
ecstatic-morse
force-pushed
the
check-consts-ref
branch
from
7f35ab6
to
7673400
Compare
|
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 |
They now look the same in the MIR after rust-lang#66587.
This checks `static mut` as well for E0017, and blesses tests now that we emit an error for a mut deref.
ecstatic-morse
force-pushed
the
check-consts-ref
branch
from
7673400
to
846be82
Compare
|
@eddyb I had to make a few changes in |
eddyb
reviewed
Nov 28, 2019
| if let LocalInfo::StaticRef { .. } = decl.local_info { | ||
| return None; | ||
| } | ||
| } |
There was a problem hiding this comment.
@matthewjasper isn't this supposed to use a helper method?
There was a problem hiding this comment.
Yes, there's body.local_decls[local].is_ref_to_static
There was a problem hiding this comment.
@matthewjasper Resolved in ccb4eed.
eddyb
reviewed
Nov 28, 2019
| | Rvalue::Ref(_, BorrowKind::Shared, ref place) | ||
| | Rvalue::Ref(_, BorrowKind::Shallow, ref place) | ||
| if matches!(place.base, PlaceBase::Static(_)) | ||
| => {} |
There was a problem hiding this comment.
Does this make sense anymore, with the static changes?
There was a problem hiding this comment.
No, this shouldn't be reachable, since the only PlaceBase::Statics are promoted. This maybe should be bug!() for now.
|
r? @matthewjasper for all the |
matthewjasper
added
S-waiting-on-author
|
@bors r=eddyb,matthewjasper |
|
📌 Commit ccb4eed has been approved by |
bors
added
S-waiting-on-bors
RalfJung
added a commit
to RalfJung/rust
that referenced
this pull request
Dec 2, 2019
…eddyb,matthewjasper Handle const-checks for `&mut` outside of `HasMutInterior` Addresses [this comment](rust-lang#64470 (comment)). Const-checking relied on `HasMutInterior` to forbid `&mut` in a const context. This was strange because all we needed to do was look for an `Rvalue::Ref` with a certain `BorrowKind`, whereas the `Qualif` traits are specifically meant to get the qualifs for a *value*. This PR removes that logic from `HasMutInterior` and moves it into `check_consts::Validator`. As a result, we can now properly handle qualifications for `static`s, which had to be ignored previously since you can e.g. borrow a static `Cell` from another `static`. We also remove the `derived_from_illegal_borrow` logic, since it is no longer necessary; we give good errors for subsequent reborrows/borrows of illegal borrows.
bors
added a commit
that referenced
this pull request
Dec 2, 2019
Rollup of 5 pull requests Successful merges: - #66245 (Conditional compilation for sanitizers) - #66654 (Handle const-checks for `&mut` outside of `HasMutInterior`) - #66822 (libunwind_panic: adjust miri panic hack) - #66827 (handle diverging functions forwarding their return place) - #66834 (rustbuild fixes) Failed merges: r? @ghost
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Addresses this comment.
Const-checking relied on
HasMutInteriorto forbid&mutin a const context. This was strange because all we needed to do was look for anRvalue::Refwith a certainBorrowKind, whereas theQualiftraits are specifically meant to get the qualifs for a value. This PR removes that logic fromHasMutInteriorand moves it intocheck_consts::Validator.As a result, we can now properly handle qualifications for
statics, which had to be ignored previously since you can e.g. borrow a staticCellfrom anotherstatic. We also remove thederived_from_illegal_borrowlogic, since it is no longer necessary; we give good errors for subsequent reborrows/borrows of illegal borrows.