You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Auto merge of #71631 - RalfJung:miri-unleash-the-gates, r=oli-obk
Miri: unleash all feature gates
IMO it is silly to unleash features that do not even have a feature gate yet, but not unleash features that do. The only thing this achieves is making unleashed mode annoying to use as we have to figure out the feature flags to enable (and not always do the error messages say what that flag is).
Given that the point of `-Z unleash-the-miri-inside-of-you` is to debug the Miri internals, I see no good reason for this extra hurdle. I cannot imagine a situation where we'd use that flag, realize the program also requires some feature gate, and then be like "oh I guess if this feature is unstable I will do something else". Instead, we'll always just add that flag to the code as well, so requiring the flag achieves nothing.
r? @oli-obk@ecstatic-morseFixes#71630
= note: The rules on what exactly is undefined behavior aren't clear, so this check might be overzealous. Please open an issue on the rustc repository if you believe it should not be considered undefined behavior.
14
8
9
+
warning: skipping const checks
10
+
|
11
+
help: skipping check that does not even have a feature gate
12
+
--> $DIR/const-points-to-static.rs:5:20
13
+
|
14
+
LL | const TEST: &u8 = &MY_STATIC;
15
+
| ^^^^^^^^^
16
+
15
17
error: aborting due to previous error; 1 warning emitted
16
18
17
19
For more information about this error, try `rustc --explain E0080`.
0 commit comments