-
-
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
rename jl/ to base/ #591
Comments
Everything in core should probably be assumed to loaded on startup. Anything in core that isn't loaded at startup should be moved into extra. |
Agreed. |
+1 I wonder if extras/ should be named something like packages/ or modules/, etc. so it is clear that it is the standard place to place additional code libraries. Many of the source files in examples/ could probably be moved in there too. I expect examples to be like an extended help file that demonstrates a complete program but several seem to be a mostly complete implementation of some data structure and without an actual example usage of it. I'm also wondering if we will need some additional organization in extras/ (or whatever it gets called). I'm thinking it would be helpful to have some sort of folder structure defined sooner rather than later. That should makes it easy to just create git submodules and (eventually) a custom package manager, without worrying too much about file name conflicts. This might get us closer to resolving #432 too. |
I believe this will conflict with other files named |
How about a better name then? |
corelib? |
How about stdlib since that's what we call it in the manual? Seems kind of windy though. |
+1 to some organisation in extras/ , a folder for each package (winston, ad ... etc) |
to me, stdlib sounds mentally confusing with the standard c header of the same name another thought is that we could go with everything being in jl/ and move everything in there now to jl/core? with an additional folder for each "package". to make loading easier, we could also have a convention that load() on a folder tries instead to load a file of the same name from within that folder (which can then load the rest of it's needs). |
That seems like a reasonable scheme to me. It helps keep all the Julia code in one place. |
Why should all the julia code be in one place? |
Tidiness? |
I still think using |
I like that. |
Stdlib: SparseArrays URL: https://github.com/JuliaSparse/SparseArrays.jl.git Stdlib branch: main Julia branch: master Old commit: 4fd3aad New commit: 5f52721 Julia version: 1.12.0-DEV SparseArrays version: 1.12.0 Bump invoked by: @ViralBShah Powered by: [BumpStdlibs.jl](https://github.com/JuliaLang/BumpStdlibs.jl) Diff: JuliaSparse/SparseArrays.jl@4fd3aad...5f52721 ``` $ git log --oneline 4fd3aad..5f52721 5f52721 Update wrappers for SuiteSparse 7.8.3 (#593) c575811 Mention vectors in more docstrings (#591) ``` Co-authored-by: ViralBShah <[email protected]>
No description provided.
The text was updated successfully, but these errors were encountered: