Use the callsite span of a macro expansion in compiletest #51848
Labels
A-diagnostics
Area: Messages for errors, warnings, and lints
A-testsuite
Area: The testsuite used to check the correctness of rustc
The following test fails, because
compiletest
does not look for the callsite span of a macro expansion:This causes some problems when the macro definition is not in the file that is tested, see issue Manishearth/compiletest-rs#48, because there is no way to expect the error with an
//~ ERROR
comment.Does the current implementation ignore the callsite of macro expansions on purpose?
If not, I have a fix for this: Manishearth/compiletest-rs#116
The text was updated successfully, but these errors were encountered: