The result of cargo machete is wrong when using macro from other crate. about cargo-machete HOT 3 CLOSED

Thanks for opening an issue! This is one of the fundamental limitations of scanning text only, so there's no right way for cargo-machete to detect this kind of cases. It's one case where cargo-udeps would not run into such an issue. We could have special annotations in the Cargo.toml indicating that a given macro implies the use of a given crate, but that might be harder to maintain. I'm curious, would such an annotation be something you'd use, or is that too much hassle? (If yes, feel free to implement it if you'd like!)

from cargo-machete.

I think such an annotation would be Ok.

As a compromise, I use

[package.metadata.cargo-machete]
ignore = []

to skip the check.

from cargo-machete.

Yep, I think the ignored annotation in the Cargo.toml makes sense and is simpler than a mapping from implicitly-used-crate to crate. So let's keep it simple and keep on recommending using the ignored annotation in that case. Thanks for opening an issue!

from cargo-machete.