This is a wrapper around cargo rustc -- --pretty=expanded
. Once installed, the
command cargo expand
prints out the result of macro expansion and #[derive]
expansion applied to the current crate.
Install with cargo install cargo-expand
.
This command optionally uses
rustfmt
to format the expanded output. The resulting code is typically much more
readable than what you get from the compiler. If rustfmt
is not available, the
expanded code is not formatted. Install rustfmt
with cargo install rustfmt
.
This command optionally uses Pygments
to colorize the
expanded output. If Pygments
is not available, the expanded code is not
colorized. Install with pip install Pygments
.
$ cat src/main.rs
```rust
[derive(Debug)]
struct S;
fn main() { println!("{:?}", S); } ```
$ cargo expand
```rust
![feature(prelude_import)]
![no_std]
[prelude_import]
use std::prelude::v1::*;
[macro_use]
extern crate std as std; struct S;
[automatically_derived]
[allow(unused_qualifications)]
impl ::std::fmt::Debug for S { fn fmt(&self, _arg0: &mut ::std::fmt::Formatter) -> ::std::fmt::Result { match *self { S => { let mut builder = _arg0.debug_tuple("S"); builder.finish() } } } }
fn main() { ::io::print(::std::fmt::Arguments::newv1({ static STATICFMTSTR: &'static [&'static str] = &["", "\n"]; _STATICFMTSTR }, &match (&S,) { (arg0,) => [::std::fmt::ArgumentV1::new(_arg0, ::std::fmt::Debug::fmt)], })); } ```
To expand a particular test target:
$ cargo expand --test test_something
To expand with rustfmt
different from the one in $PATH
:
$ RUSTFMT=/path/to/rustfmt cargo expand
To expand without rustfmt
even though it is available in $PATH
:
$ RUSTFMT= cargo expand
To color with pygmentize
different from the one in $PATH
:
$ PYGMENTIZE=/path/to/pygmentize cargo expand
To not color even though pygmentize
is available in $PATH
:
$ PYGMENTIZE= cargo expand
Be aware that macro expansion to text is a lossy process. This is a debugging aid only. There should be no expectation that the expanded code can be compiled successfully, nor that if it compiles then it behaves the same as the original code.
For instance the following function returns 3
when compiled ordinarily by Rust
but the expanded code compiles and returns 4
.
```rust fn f() -> i32 { let x = 1;
macro_rules! first_x {
() => { x }
}
let x = 2;
x + first_x!()
} ```
Refer to [The Book] for more on the considerations around macro hygiene.
Licensed under either of
at your option.
Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in cargo-expand by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.