No expansion backtrace for macro where contents does not parse #23243
Labels
A-diagnostics
Area: Messages for errors, warnings, and lints
A-macros
Area: All kinds of macros (custom derive, macro_rules!, proc macros, ..)
C-bug
Category: This is a bug.
The error messages should point to the respective
foo!
invocations, not just the contents of the macro, likeThe text was updated successfully, but these errors were encountered: