Skip to content
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

Closed
StefanKarpinski opened this issue Mar 15, 2012 · 14 comments
Closed

rename jl/ to base/ #591

StefanKarpinski opened this issue Mar 15, 2012 · 14 comments
Assignees
Milestone

Comments

@StefanKarpinski
Copy link
Member

No description provided.

@ghost ghost assigned StefanKarpinski Mar 15, 2012
@aviks
Copy link
Member

aviks commented Mar 15, 2012

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.

@StefanKarpinski
Copy link
Member Author

Agreed.

@vtjnash
Copy link
Member

vtjnash commented Mar 19, 2012

+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.

@JeffBezanson
Copy link
Member

I believe this will conflict with other files named core that I often have in this directory :)

@StefanKarpinski
Copy link
Member Author

How about a better name then?

@JeffBezanson
Copy link
Member

corelib?

@StefanKarpinski
Copy link
Member Author

How about stdlib since that's what we call it in the manual? Seems kind of windy though.

@aviks
Copy link
Member

aviks commented Mar 19, 2012

+1 to some organisation in extras/ , a folder for each package (winston, ad ... etc)

@vtjnash
Copy link
Member

vtjnash commented Mar 19, 2012

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).

@StefanKarpinski
Copy link
Member Author

That seems like a reasonable scheme to me. It helps keep all the Julia code in one place.

@JeffBezanson
Copy link
Member

Why should all the julia code be in one place?

@StefanKarpinski
Copy link
Member Author

Tidiness?

@JeffBezanson
Copy link
Member

I still think using core is a bad idea. How about base? Then we can also call the namespace of the standard library Base which is nice and short.

@StefanKarpinski
Copy link
Member Author

I like that.

LilithHafner pushed a commit to LilithHafner/julia that referenced this issue Oct 11, 2021
ViralBShah added a commit that referenced this issue Jan 13, 2025
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]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants