Replies: 1 comment 1 reply
-
|
You can try the assist "Inline macro", which expands the macro once. It is not available for attribute/derive macros, though. You may also be interested in #19130. |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
In this case, there are several layers of macro_rules. I tried inlining them as needed but I find it more confusing than just looking at the whole output. +1 for #19130. Looks promising, subscribed. |
Beta Was this translation helpful? Give feedback.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I'm working with macro_rules that output over 1kloc per callsite and not having any hints in the macro expansion is a pain point.
At this time I'm limited to:
It works except whenever there are std macros mixed in. Macros like
format!expand toalloc::__export::must_usewhich drowns-out interesting hints with errors like "use of unstable library featurehint_must_use".Is there a way to get around that on stable?
If RA could be configured to not expand std macros and to copy over whatever imports are in scope at the macro callsite, in the macro expansion, that might be enough to have much better DX with macro_rules.
Thank you for RA, it's the best.
Beta Was this translation helpful? Give feedback.
All reactions