diff options
| author | Michael Goulet <michael@errs.io> | 2024-11-22 21:07:40 -0500 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2024-11-22 21:07:40 -0500 |
| commit | bb92131dabf41c6a554718bd2d2e150f38c565b4 (patch) | |
| tree | 970d829bfa623133f52c23d312669bcc85a848f5 /compiler/rustc_llvm/llvm-wrapper | |
| parent | 7b40a9b7c62878cb9cb7cc8e80d23c819b2d6c8f (diff) | |
| parent | 660246bc762c426a9f46a212ee4b35b0d54256c1 (diff) | |
| download | rust-bb92131dabf41c6a554718bd2d2e150f38c565b4.tar.gz rust-bb92131dabf41c6a554718bd2d2e150f38c565b4.zip | |
Rollup merge of #133159 - Zalathar:unstable-options-no-value, r=jieyouxu
Don't allow `-Zunstable-options` to take a value Passing an explicit boolean value (`-Zunstable-options=on`, `off` etc.) sometimes appears to work, but actually puts the compiler into an unintended state where unstable _options_ are still forbidden, but unstable values of _some_ stable options are allowed. This is a result of `-Zunstable-options` being checked in multiple different places, in slightly different ways. Fixing the checks in `config::nightly_options` to understand boolean values would be non-trivial, so for now it's easier to make things consistent by forbidding values in the `-Z` parser. --- There were a few uses of this in tests, which happened to work because they were tests of unstable values.
Diffstat (limited to 'compiler/rustc_llvm/llvm-wrapper')
0 files changed, 0 insertions, 0 deletions
