-
Notifications
You must be signed in to change notification settings - Fork 49
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Analyze and forbid dependency from one mod to another? #219
Comments
For "dependency" (/"uses") relationships though need to add the 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 |
Thank you for the information!
So I wonder will this be implemented in the future? |
I very much hope so! The tool uses 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 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. |
I see, thank you! |
You may want to watch this one #227 😉 |
Wow that looks great, thank you! 😄 |
Hi thanks for the tool! Given the
acyclic
option, I guess this crate does analyze all dependencies between mods. However, it seems that currently it only outputs adot
graph that shows the ownership between modules, instead of dependency relationship.In my case, say I have mod A, B, C. I want to check automatically that, the mod A is never used by mod B (but can be used by mod C), such that it satisfies things like layered architecture.
The text was updated successfully, but these errors were encountered: