Richard Schneeman on Nostr: Is there a trick to allowing a proc macro to take the output of a declarative macro ...

Is there a trick to allowing a proc macro to take the output of a declarative macro as an input?

I would think that writing a declarative macro wrapper than yields the proc macro would work but it doesn't seem to.

Since I cannot write a macro that behaves like `include_str!` I want my declarative macro to accept the output of `include_str!`, however it due to resolution order, it gets the literal code (and not the output).

#rust