croc-look is a tool to make testing and debuging proc macros easier by these two features
- Printing the output of the procedural macro code to the console.
- Giving a real time live view of the output of the macro on rust code.
croc-look allows you to narrow down your search and also provide real time view of the generated code.
croc-look requires a nightly toolchain installed, it does not need to be the default toolchain
rustup install nightly
Then
cargo install croc-look
--trait-impl
or-t
: Defines the trait you want to see the expansion off, this is gonna be the trait your derive macro is implementing or it could be any other trait you want to see the expansion off. For example
#[derive(Clone, Debug, MyTrait)]
struct<T> {
...
}
So the value for this flag can be either Clone
, Debug
or whatever trait your MyTrait
derive macro is implementing
-
--impl-for
or-i
: This helps you narrow down your search for a trait impl for the flag mentioned above. If you have multiple structs deriving your trait then you can docroc-look --trait-impl Clone -i <your-struct-name>
and get the impl for the struct you want. -
--structure
or-s
: If you want to expand a particlar struct. This is useful when a macro is manupilating the struct itself, like adding fields, etc. -
--path
or-p
: (requies cargo expand to be installed) Usecargo expand <path>
internally to narrow down code to modules. egcroc-look -p cmd -t Clone -i Context
(This finds the impl Clone for Context in cmd module) -
--function
or-f
: For expanding a function. -
--binary
or-b
: To expand acargo --bin BINARY
, if not specified then--lib
is used -
--watch
or-w
: This starts watching the directory/file you want to watch, this also opens up an interactive TUI which has support for live reloading changes as you do them in your proc-macro project.
How is this different from cargo expand?
cargo expand doesn't allow you to view a whole trait impl to check generics or watch particular code blocks. The motive of croc-look is to narroy arry down your search to a simple single body and reduce cluter.
You can use the --path
flag to use cargo expand <path>
to narrow down searches module level