diff options
| author | Ömer Sinan Ağacan <omeragacan@gmail.com> | 2021-02-27 13:37:50 +0300 |
|---|---|---|
| committer | Ömer Sinan Ağacan <omeragacan@gmail.com> | 2021-02-27 14:06:57 +0300 |
| commit | 992b914b6bf41aae4212ea4e8ee09f8b16a31f28 (patch) | |
| tree | 354a37698a7a8d61a905b083e5b5e133af586c5a /compiler/rustc_mir/src/transform/coverage/debug.rs | |
| parent | fb631a55c2acfae37e55e4c338dd3cc03da0fa7f (diff) | |
| download | rust-992b914b6bf41aae4212ea4e8ee09f8b16a31f28.tar.gz rust-992b914b6bf41aae4212ea4e8ee09f8b16a31f28.zip | |
Recover from X<Y,Z> when parsing const expr
This adds recovery when in array type syntax user writes
[X; Y<Z, ...>]
instead of
[X; Y::<Z, ...>]
Fixes #82566
Note that whenever we parse an expression and know that the next token
cannot be `,`, we should be calling
check_mistyped_turbofish_with_multiple_type_params for this recovery.
Previously we only did this for statement parsing (e.g. `let x = f<a,
b>;`). We now also do it when parsing the length field in array type
syntax.
Diffstat (limited to 'compiler/rustc_mir/src/transform/coverage/debug.rs')
0 files changed, 0 insertions, 0 deletions