rust/tests/ui/resolve/token-error-correct-3.stderr

error: expected one of `)`, `,`, `.`, `?`, or an operator, found `;`
  --> $DIR/token-error-correct-3.rs:13:21
   |
LL |             callback(path.as_ref();
   |                     ^             ^ help: `)` may belong here
   |                     |
   |                     unclosed delimiter

error: expected one of `.`, `;`, `?`, `}`, or an operator, found `)`
  --> $DIR/token-error-correct-3.rs:16:9
   |
LL |             fs::create_dir_all(path.as_ref()).map(|()| true)
   |                                                             - expected one of `.`, `;`, `?`, `}`, or an operator
LL |         } else {
   |         ^ unexpected token

error[E0425]: cannot find function `is_directory` in this scope
  --> $DIR/token-error-correct-3.rs:11:13
   |
LL |         if !is_directory(path.as_ref()) {
   |             ^^^^^^^^^^^^ not found in this scope

error: aborting due to 3 previous errors

For more information about this error, try `rustc --explain E0425`.
Emit missing unclosed delimiter errors 2019-03-03 12:14:25 -08:00			error: expected one of `)`, `,`, `.`, `?`, or an operator, found `;`
Point at unclosed delimiters as part of the primary MultiSpan Both the place where the parser encounters a needed closed delimiter and the unclosed opening delimiter are important, so they should get the same level of highlighting in the output. 2021-08-27 10:57:28 +00:00			`--> $DIR/token-error-correct-3.rs:13:21`
Emit missing unclosed delimiter errors 2019-03-03 12:14:25 -08:00			`\|`
			`LL \| callback(path.as_ref();`
Point at unclosed delimiters as part of the primary MultiSpan Both the place where the parser encounters a needed closed delimiter and the unclosed opening delimiter are important, so they should get the same level of highlighting in the output. 2021-08-27 10:57:28 +00:00			\| ^ ^ help: `)` may belong here
Fix #58270, fix off-by-one error in error diagnostics. 2019-04-16 19:26:41 -03:00			`\| \|`
Collect unclosed delimiters in parent parser 2019-03-03 12:45:49 -08:00			`\| unclosed delimiter`

			error: expected one of `.`, `;`, `?`, `}`, or an operator, found `)`
Drop support for cloudabi targets 2020-10-27 13:10:31 +00:00			`--> $DIR/token-error-correct-3.rs:16:9`
Collect unclosed delimiters in parent parser 2019-03-03 12:45:49 -08:00			`\|`
			`LL \| fs::create_dir_all(path.as_ref()).map(\|()\| true)`
Remove "here" from "expected one of X here" 2019-10-28 11:08:53 -07:00			\| - expected one of `.`, `;`, `?`, `}`, or an operator
Collect unclosed delimiters in parent parser 2019-03-03 12:45:49 -08:00			`LL \| } else {`
			`\| ^ unexpected token`
Move some compile-fail tests into UI directory 2016-12-01 01:35:25 +03:00
resolve: Do not use "resolve"/"resolution" in error messages 2017-01-12 01:18:08 +03:00			error[E0425]: cannot find function `is_directory` in this scope
Drop support for cloudabi targets 2020-10-27 13:10:31 +00:00			`--> $DIR/token-error-correct-3.rs:11:13`
Move some compile-fail tests into UI directory 2016-12-01 01:35:25 +03:00			`\|`
Emit missing unclosed delimiter errors 2019-03-03 12:14:25 -08:00			`LL \| if !is_directory(path.as_ref()) {`
resolve: Do not use "resolve"/"resolution" in error messages 2017-01-12 01:18:08 +03:00			`\| ^^^^^^^^^^^^ not found in this scope`
Move some compile-fail tests into UI directory 2016-12-01 01:35:25 +03:00
Do not emit type errors after parse error in last statement of block When recovering from a parse error inside a block, do not emit type errors generating on that block's recovered return expression. Fix #57383. 2019-07-12 18:37:57 -07:00			`error: aborting due to 3 previous errors`
Move some compile-fail tests into UI directory 2016-12-01 01:35:25 +03:00
Do not emit type errors after parse error in last statement of block When recovering from a parse error inside a block, do not emit type errors generating on that block's recovered return expression. Fix #57383. 2019-07-12 18:37:57 -07:00			For more information about this error, try `rustc --explain E0425`.