diff options
| author | Jubilee <workingjubilee@gmail.com> | 2024-11-09 20:28:46 -0800 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2024-11-09 20:28:46 -0800 |
| commit | c19d56c90229fcf8a70bdcb891a1ede5d8044ecf (patch) | |
| tree | 8d6151aafb3fc27982e8785041796f0bb8228e50 /compiler/rustc_monomorphize/src | |
| parent | 0ba177083fa81e380e28e445c25b6aff35279bbc (diff) | |
| parent | 935bf6995f7cad774b12168b76d8253285a4101e (diff) | |
| download | rust-c19d56c90229fcf8a70bdcb891a1ede5d8044ecf.tar.gz rust-c19d56c90229fcf8a70bdcb891a1ede5d8044ecf.zip | |
Rollup merge of #132828 - est31:let_chains_parsing_tests, r=compiler-errors
Additional tests to ensure let is rejected during parsing In the original stabilization PR, @ `compiler-errors` has [pointed out](https://github.com/rust-lang/rust/pull/94927#issuecomment-1165156328) that #97295 wasn't enough to address the concerns about having `let` in expressions being rejected at parsing time, instead of later. Thankfully, since then the situation has been greatly improved by #115677. This PR adds some additional tests to `disallowed-positions.rs`, and adds two additional revisions to the "normal" case which is now given the `feature` name: * `no_feature`: Added to incorporate `disallowed-positions-without-feature-gate.rs` into the file, reducing duplication. * `nothing`: like feature, but all functions are cfg'd out. Ensures that the errors are really emitted during parsing. cc tracking issue #53667
Diffstat (limited to 'compiler/rustc_monomorphize/src')
0 files changed, 0 insertions, 0 deletions