rust/tests/ui/parser/issues/issue-20616-3.stderr

error: expected one of `>`, a const expression, lifetime, or type, found `,`
  --> $DIR/issue-20616-3.rs:13:24
   |
LL | type Type_3<T> = Box<T,,>;
   |                        ^ expected one of `>`, a const expression, lifetime, or type
   |
help: you might have meant to end the type parameters here
   |
LL | type Type_3<T> = Box<T>,,>;
   |                       +

error: aborting due to 1 previous error
Fix UI tests for 'const expression' change 2020-12-04 11:21:33 +00:00			error: expected one of `>`, a const expression, lifetime, or type, found `,`
Adjust parser generic parameter errors 2019-02-07 09:10:11 +00:00			`--> $DIR/issue-20616-3.rs:13:24`
Move some `compile-fail` tests to `ui` 2018-07-15 21:11:54 +00:00			`\|`
Adjust parser generic parameter errors 2019-02-07 09:10:11 +00:00			`LL \| type Type_3<T> = Box<T,,>;`
Fix UI tests for 'const expression' change 2020-12-04 11:21:33 +00:00			\| ^ expected one of `>`, a const expression, lifetime, or type
Provide suggestion for missing `>` in a type parameter list When encountering an inproperly terminated type parameter list, provide a suggestion to close it after the last non-constraint type parameter that was successfully parsed. Fix #94058. 2022-03-01 19:40:48 +00:00			`\|`
			`help: you might have meant to end the type parameters here`
			`\|`
			`LL \| type Type_3<T> = Box<T>,,>;`
			`\| +`
Move some `compile-fail` tests to `ui` 2018-07-15 21:11:54 +00:00
Show number in error message even for one error Co-authored-by: Adrian <adrian.iosdev@gmail.com> 2023-11-21 15:44:16 +00:00			`error: aborting due to 1 previous error`
Move some `compile-fail` tests to `ui` 2018-07-15 21:11:54 +00:00