diff options
| author | Matthias Krüger <matthias.krueger@famsik.de> | 2023-01-28 05:20:17 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2023-01-28 05:20:17 +0100 |
| commit | 260e04879ee52a768a66ad131c7bd1b56526e609 (patch) | |
| tree | dbdcb9d5a3ad0ced7eb45745a54a78b831a8aeef /library/std/src/sys/unix/stack_overflow.rs | |
| parent | 3b6593a0b4e41d680ddc196ce47ee649be62a660 (diff) | |
| parent | 80a1536c7ab73c867d5a60f4441058e7e2231d8d (diff) | |
| download | rust-260e04879ee52a768a66ad131c7bd1b56526e609.tar.gz rust-260e04879ee52a768a66ad131c7bd1b56526e609.zip | |
Rollup merge of #107190 - fmease:fix-81698, r=compiler-errors
Recover from more const arguments that are not wrapped in curly braces
Recover from some array, borrow, tuple & arithmetic expressions in const argument positions that lack curly braces and provide a suggestion to fix the issue continuing where #92884 left off. Examples of such expressions: `[]`, `[0]`, `[1, 2]`, `[0; 0xff]`, `&9`, `("", 0)` and `(1 + 2) * 3` (we previously did not recover from them).
I am not entirely happy with my current solution because the code that recovers from `[0]` (coinciding with a malformed slice type) and `[0; 0]` (coinciding with a malformed array type) is quite fragile as the aforementioned snippets are actually successfully parsed as types by `parse_ty` since it itself already recovers from them (returning `[⟨error⟩]` and `[⟨error⟩; 0]` respectively) meaning I have to manually look for `TyKind::Err`s and construct a separate diagnostic for the suggestion to attach to (thereby emitting two diagnostics in total).
Fixes #81698.
`@rustbot` label A-diagnostics
r? diagnostics
Diffstat (limited to 'library/std/src/sys/unix/stack_overflow.rs')
0 files changed, 0 insertions, 0 deletions