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 emitted const _: 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.
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.