-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Dependency tree of stdlibs #25951
Comments
Nice, +1 to breaking dependency edges. Distributed only uses LinearAlgebra in order to call Another one I noticed: SharedArrays uses a single sprintf call that could easily be replaced. |
I also just noticed we have a cycle: |
|
Is it actually a DAG now? |
GraphViz/dot says yes:
Sorry, my analysis applies to the 1.0.2 release, of course, not some branch where refactoring is happening. |
Nice graph! |
Yes, very nice graph! This dependency graph is starting to look a bit more reasonable. |
|
Very good, this looks quite reasonable. |
Wow, that's such a nice, sane dependency graph now! |
Fantastic work! ❤️ 🎉 |
Close? |
Below is the dependency graph of our stdlib:
There are a few unfortunate dependencies. One for example is the Test --> Distributed --> LinearAlgebra, which means that you cannot use the Test stdlib without having the LinearAlgebra stdlib.
Perhaps some refactorings to avoid this would be useful. Test uses only
myid
from Distributed for example.Figure created with:
The text was updated successfully, but these errors were encountered: