This seems possibly helpful for people writing proc-macro's to see how they interact? If the original issue is something you want I'd take a look at it.

I'm debugging a proc macro right now which generates a declarative macro invocation. Something's wrong about the generated declarative macro invocation, but it's hard to investigate because the invocation is expanded immediately.

This would certainly be a useful feature to have, at least for debugging proc macros

Although this need could also be solved with #68, by setting the expanded crate to the proc macro crate

Uh oh!

Flag to control how deeply macros are expanded #11

Description

Metadata

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Issue actions