MACRO: Fix macro expansion error messages in several cases #9095
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
#[cfg()]
attribute" in the case of cfg-disabled macro call that refers to a declarative macro. Previously there was some other unrelated error message. For example "procedural macro expansion is not enabled" iforg.rust.cargo.evaluate.build.scripts
and/ororg.rust.macros.proc
experimental features are disabled.org.rust.cargo.evaluate.build.scripts
and/ororg.rust.macros.proc
experimental features are disabled. Previously the error was "the procedural macro is not compiled successfully"Also add tests for these cases.
changelog: Fix error messages about unsuccessful macro expansion in the case when procedural macro expansion is not enabled and in the case when a declarative macro call is conditionally disabled