rust/tests/ui/parser/issues/issue-84148-1.stderr

error: invalid `?` in type
  --> $DIR/issue-84148-1.rs:1:14
   |
LL | fn f(t:for<>t?)
   |              ^ `?` is only allowed on expressions, not types
   |
help: if you meant to express that the type might not contain a value, use the `Option` wrapper type
   |
LL | fn f(t:Option<for<>t>)
   |        +++++++      ~

error: expected one of `->`, `where`, or `{`, found `<eof>`
  --> $DIR/issue-84148-1.rs:1:15
   |
LL | fn f(t:for<>t?)
   |               ^ expected one of `->`, `where`, or `{`

error: aborting due to 2 previous errors
Parse `Ty?` as `Option<Ty>` and provide structured suggestion Swift has specific syntax that desugars to `Option<T>` similar to our `?` operator, which means that people might try to use it in Rust. Parse it and gracefully recover. 2022-01-10 16:02:19 -06:00			error: invalid `?` in type
Remove incorrect assertion in type parsing code 2021-06-04 12:48:24 -05:00			`--> $DIR/issue-84148-1.rs:1:14`
			`\|`
			`LL \| fn f(t:for<>t?)`
Parse `Ty?` as `Option<Ty>` and provide structured suggestion Swift has specific syntax that desugars to `Option<T>` similar to our `?` operator, which means that people might try to use it in Rust. Parse it and gracefully recover. 2022-01-10 16:02:19 -06:00			\| ^ `?` is only allowed on expressions, not types
Remove incorrect assertion in type parsing code 2021-06-04 12:48:24 -05:00			`\|`
Parse `Ty?` as `Option<Ty>` and provide structured suggestion Swift has specific syntax that desugars to `Option<T>` similar to our `?` operator, which means that people might try to use it in Rust. Parse it and gracefully recover. 2022-01-10 16:02:19 -06:00			help: if you meant to express that the type might not contain a value, use the `Option` wrapper type
			`\|`
			`LL \| fn f(t:Option<for<>t>)`
			`\| +++++++ ~`
Remove incorrect assertion in type parsing code 2021-06-04 12:48:24 -05:00
Do not add `;` to expected tokens list when it's wrong There's a few spots where semicolons are checked for to do error recovery, and should not be suggested (or checked for other stuff). Fixes #87647 2021-12-04 12:05:30 -06:00			error: expected one of `->`, `where`, or `{`, found `<eof>`
Remove incorrect assertion in type parsing code 2021-06-04 12:48:24 -05:00			`--> $DIR/issue-84148-1.rs:1:15`
			`\|`
			`LL \| fn f(t:for<>t?)`
Do not add `;` to expected tokens list when it's wrong There's a few spots where semicolons are checked for to do error recovery, and should not be suggested (or checked for other stuff). Fixes #87647 2021-12-04 12:05:30 -06:00			\| ^ expected one of `->`, `where`, or `{`
Remove incorrect assertion in type parsing code 2021-06-04 12:48:24 -05:00
Parse `Ty?` as `Option<Ty>` and provide structured suggestion Swift has specific syntax that desugars to `Option<T>` similar to our `?` operator, which means that people might try to use it in Rust. Parse it and gracefully recover. 2022-01-10 16:02:19 -06:00			`error: aborting due to 2 previous errors`
Remove incorrect assertion in type parsing code 2021-06-04 12:48:24 -05:00