You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Tool author here. I wrote cargo-inspect because I wanted to know more about the inner workings of Rust. The compiler actually provides a lot of information that tools like cargo-inspect can simply format and visualize.
It works best with small input snippets, but it also supports crates. Just keep in mind that the output can be a bit overwhelming in that case.
For a similar tool that uses the same compiler internals but formats it a little differently, try cargo-expand.
It is more well-maintained, but cargo-inspect also supports diffing two snippets to see the changes the compiler makes.
Activity
mre commentedon Jun 18, 2020
Tool author here. I wrote cargo-inspect because I wanted to know more about the inner workings of Rust. The compiler actually provides a lot of information that tools like cargo-inspect can simply format and visualize.
It works best with small input snippets, but it also supports crates. Just keep in mind that the output can be a bit overwhelming in that case.
I gave a talk about the tool at FOSDEM, Brussels 2019 here.
For a similar tool that uses the same compiler internals but formats it a little differently, try cargo-expand.
It is more well-maintained, but cargo-inspect also supports diffing two snippets to see the changes the compiler makes.