diff options
| author | Mara Bos <m-ou.se@m-ou.se> | 2020-11-16 17:26:38 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2020-11-16 17:26:38 +0100 |
| commit | e6b6c8e4fc63b2229e4db079510c1dac26917437 (patch) | |
| tree | 4f3c7a87cf0dadf0ddc4485c9d823ac351058844 /compiler/rustc_llvm/llvm-wrapper/RustWrapper.cpp | |
| parent | c3da682249d2d6fc80735e8b0da8be4b2451f551 (diff) | |
| parent | 0bc04e327c54db788b0a7093879e3c4e51301356 (diff) | |
| download | rust-e6b6c8e4fc63b2229e4db079510c1dac26917437.tar.gz rust-e6b6c8e4fc63b2229e4db079510c1dac26917437.zip | |
Rollup merge of #79087 - ThePuzzlemaker:issue-79083-docfix, r=RalfJung
Update E0744 about control flow in `const` contexts to accurately describe when the error is triggered and why This PR fixes #79083. `const fn` currently supports `if`, `match`, `loop`, and `while` in terms of control flow. The error relating to control flow in `const` contexts currently states that those control flow constructs are not allowed in `const` contexts. That is no longer true, as RFC 2342 and 2344 were [stabilized](https://github.com/rust-lang/rust/pull/72437). `for` loops, however, as well as `?` and `.await` are still not allowed, so I changed the error message to be more descriptive of the error as it is not just control flow that could trigger this error. I also added links to tracking issues that mark things that are blocking the usage of these expressions.
Diffstat (limited to 'compiler/rustc_llvm/llvm-wrapper/RustWrapper.cpp')
0 files changed, 0 insertions, 0 deletions