forked from rust-lang/rust
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Rollup merge of rust-lang#85564 - pnkfelix:issue-85435-readd-capture-…
…disjoint-fields-gate, r=nikomatsakis readd capture disjoint fields gate This readds a feature gate guard that was added in PR rust-lang#83521. (Basically, there were unintended consequences to the code exposed by removing the feature gate guard.) The root bug still remains to be resolved, as discussed in issue rust-lang#85561. This is just a band-aid suitable for a beta backport. Cc issue rust-lang#85435 Note that the latter issue is unfixed until we backport this (or another fix) to 1.53 beta
- Loading branch information
Showing
2 changed files
with
47 additions
and
15 deletions.
There are no files selected for viewing
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
27 changes: 27 additions & 0 deletions
27
src/test/ui/unsafe/issue-85435-unsafe-op-in-let-under-unsafe-under-closure.rs
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,27 @@ | ||
// check-pass | ||
// revisions: mir thir | ||
// [thir]compile-flags: -Z thir-unsafeck | ||
|
||
// This is issue #85435. But the real story is reflected in issue #85561, where | ||
// a bug in the implementation of feature(capture_disjoint_fields) () was | ||
// exposed to non-feature-gated code by a diagnostic changing PR that removed | ||
// the gating in one case. | ||
|
||
// This test is double-checking that the case of interest continues to work as | ||
// expected in the *absence* of that feature gate. At the time of this writing, | ||
// enabling the feature gate will cause this test to fail. We obviously cannot | ||
// stabilize that feature until it can correctly handle this test. | ||
|
||
fn main() { | ||
let val: u8 = 5; | ||
let u8_ptr: *const u8 = &val; | ||
let _closure = || { | ||
unsafe { | ||
let tmp = *u8_ptr; | ||
tmp | ||
|
||
// Just dereferencing and returning directly compiles fine: | ||
// *u8_ptr | ||
} | ||
}; | ||
} |