mikros/rust
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
a20078f044
rust/tests/ui/parser/issues/issue-84148-2.stderr

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

28 lines
706 B
Plaintext
Raw Normal View History

Remove incorrect assertion in type parsing code
2021-06-04 12:48:24 -05:00
error: this file contains an unclosed delimiter
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
--> $DIR/issue-84148-2.rs:3:16
Remove incorrect assertion in type parsing code
2021-06-04 12:48:24 -05:00
|
LL | fn f(t:for<>t?
| - ^
| |
| unclosed delimiter
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
--> $DIR/issue-84148-2.rs:3:14
Remove incorrect assertion in type parsing code
2021-06-04 12:48:24 -05:00
|
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>`
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
--> $DIR/issue-84148-2.rs:3:16
Remove incorrect assertion in type parsing code
2021-06-04 12:48:24 -05:00
|
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 3 previous errors
Remove incorrect assertion in type parsing code
2021-06-04 12:48:24 -05:00
Reference in New Issue Copy Permalink