rust/tests/ui/proc-macro/issue-81543-item-parse-err.stderr

error: expected identifier, found `32`
  --> $DIR/issue-81543-item-parse-err.rs:11:8
   |
LL |     fn 32() {}
   |        ^^ expected identifier

error: aborting due to 1 previous error
Improve handling of spans around macro result parse errors Fixes #81543 After we expand a macro, we try to parse the resulting tokens as a AST node. This commit makes several improvements to how we handle spans when an error occurs: * Only ovewrite the original `Span` if it's a dummy span. This preserves a more-specific span if one is available. * Use `self.prev_token` instead of `self.token` when emitting an error message after encountering EOF, since an EOF token always has a dummy span * Make `SourceMap::next_point` leave dummy spans unused. A dummy span does not have a logical 'next point', since it's a zero-length span. Re-using the span span preserves its 'dummy-ness' for other checks 2021-01-31 20:21:28 +00:00			error: expected identifier, found `32`
			`--> $DIR/issue-81543-item-parse-err.rs:11:8`
			`\|`
			`LL \| fn 32() {}`
			`\| ^^ expected identifier`

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`
Improve handling of spans around macro result parse errors Fixes #81543 After we expand a macro, we try to parse the resulting tokens as a AST node. This commit makes several improvements to how we handle spans when an error occurs: * Only ovewrite the original `Span` if it's a dummy span. This preserves a more-specific span if one is available. * Use `self.prev_token` instead of `self.token` when emitting an error message after encountering EOF, since an EOF token always has a dummy span * Make `SourceMap::next_point` leave dummy spans unused. A dummy span does not have a logical 'next point', since it's a zero-length span. Re-using the span span preserves its 'dummy-ness' for other checks 2021-01-31 20:21:28 +00:00