Fix non_upper_case_globals lint in some cases #154
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.
This was never reported as a bug, but mentioned on the discord, that sometimes the macro emits warnings that can be ignored with
#![allow(non_upper_case_globals)]
. I believe the culprit in the situation is the emittedconst _:
when parts of the style AST can be constructed at compile time.I've added a small comment on the usage of
Span::mixed_site()
for future reference too, since I had to look that up when editing.