Analyze and forbid dependency from one mod to another?

[fzyzcjy]

Analyze and forbid dependency from one mod to another?

[regexident]

For "dependency" (/"uses") relationships though need to add the --uses flag to your cargo modules generate graph … command (which has --no-uses as implicit default).

That said there currently is no way (yet) for the tool to detect dependencies from function bodies though, which is an admittedly big blind spot of the --uses flag.

[fzyzcjy]

Thank you for the information!

That said there currently is no way (yet) for the tool to detect dependencies from function bodies though, which is an admittedly big blind spot of the --uses flag.

So I wonder will this be implemented in the future?

[regexident]

I very much hope so!

The tool uses rust-analyzer (RA) as a library dependency and I simply haven't yet been able to fully figure out how walk the types used inside a function body.

The internal API of RA is mostly rather sparsely documented, and often very indirect in nature due to its extensive use of interning, which makes navigating it somewhat difficult as an outsider. As such implementing a new feature in cargo-modules frequently turns into first having to search the RA codebase for potentially useful types and methods and then trying to figure out how to actually use them by reading through any usages within RA itself. The function body stuff has been particularly opaque so far, as it doesn't seem to work like the rest of RA. I recently found a possible approach but unfortunately ultimately couldn't manage to make it work. I'm not giving up just yet though.

Occasionally I've asked the RA devs for help on their Zulip but it feels kinda bad to ask them for customer support for their private API that isn't really intended for public use, afaict.

[fzyzcjy]

I see, thank you!

[regexident]

You may want to watch this one #227 😉

[fzyzcjy]

Wow that looks great, thank you! 😄