cargo-expand VS cargo-edit

It's been superseded by https://github.com/dtolnay/cargo-expand

Try installing cargo expand, it's useful to see how macros eventually get expanded. For example, if you run cargo expand on the following code

You can use cargo expand to see what your code expands to: https://github.com/dtolnay/cargo-expand

Not too familiar with macros but does cargo-expand do what you want or did you mean something else?

Yes. You can use Tools > Expand Macro on the playground or install and run cargo-expand to see what the macro expands to. It just adds a & before the argument.

cargo expand

Along with what others are saying, there is also cargo expand which can show you what code a macro generates

Something that may help you understand code with magic proc macros is this utility. It's basically a wrapper around a Rust compiler flag that allows you to expand macros for a file.

You can use https://github.com/dtolnay/cargo-expand to examine how it works.

“cargo add” from https://github.com/killercup/cargo-edit has that behavior, but not the built in one that was added to cargo

I have also noticed that the last commit of cargo-edit crate's GitHub repo (https://github.com/killercup/cargo-edit) was two days ago (pretty recent.) So it is probably relevant for a lot of people.

cargo-upgrade from cargo-edit (somewhat more intentional than builtin update)

I've also tried cargo-upgrade from cargo-edit like so:

You can also see how other crates do it. For example, cargo-edit is just like that - a single package with a library with a couple of small cli wrappers around it. You can compare their Cargo.toml to yours, maybe there is something different about them.

Just to check, are you aware of cargo-edit's cargo-set-version or cargo-release?

Speaking of cargo remove, see also cargo-edit [0] from which adding and removing originally came, as well as cargo-binstall [1] which installs binaries rather than compiling from source every time. The binaries are updatable with cargo-update [2].

The latter two can replace a package manager for Rust related utilities, as I often find that those in OS package repositories are often not as up to date as directly from cargo.

[0] https://github.com/killercup/cargo-edit

[1] https://github.com/cargo-bins/cargo-binstall

[2] https://github.com/nabijaczleweli/cargo-update

For context, it was/is part of cargo-edit crate which provides other nice functionalities as well. Hope all gets integrated in time.

https://github.com/killercup/cargo-edit can use the F option