diff options
| author | Matthias Krüger <matthias.krueger@famsik.de> | 2022-06-26 19:47:01 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2022-06-26 19:47:01 +0200 |
| commit | 7312a66a5c8e54b68aedbbd779c829f3709f5460 (patch) | |
| tree | 812d14103c85c913815b6db52ab356c5333c46a0 /compiler/rustc_parse/src/parser | |
| parent | 5b312710d509e75b5d52b77d56e2d34ec2038696 (diff) | |
| parent | 3899914131053cafb46f61ba3c7d6846673ebd22 (diff) | |
| download | rust-7312a66a5c8e54b68aedbbd779c829f3709f5460.tar.gz rust-7312a66a5c8e54b68aedbbd779c829f3709f5460.zip | |
Rollup merge of #97743 - RalfJung:const-err-future-breakage, r=estebank
make const_err show up in future breakage reports As tracked in https://github.com/rust-lang/rust/issues/71800, const_err should become a hard error Any Day Now (TM). I'd love to move forward with that sooner rather than later; it has been deny-by-default for many years and a future incompat lint since https://github.com/rust-lang/rust/pull/80394 (landed more than a year ago). Some CTFE errors are already hard errors since https://github.com/rust-lang/rust/pull/86194. But before we truly make it a hard error in all cases, we now have one more intermediate step we can take -- to make it show up in future breakage reports. Cc `````@rust-lang/wg-const-eval`````
Diffstat (limited to 'compiler/rustc_parse/src/parser')
0 files changed, 0 insertions, 0 deletions