Initial setup to move modules out of Base to a stdlib #19628
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is an initial attempt at the creation of a
stdlib
separate from Base (discussed here).While the full list of features/steps/functionality listed in the above issue is out of scope for 0.6, I still think there are some concrete advantages to starting the process:
stdlib
at least enables a still-manual-but-less-complicated way to build a "julia lite" (where a user could just remove thestdlib
includes fromsysimg.jl
I think there's enough to think about and iron out just in this "step 1" of the process that, we might as well kick off the process.
Two questions I came up with, just putting together this PR were:
julia -exclude=quadgk,linalg
which would result in thosestdlib
modules not being included in the build julia; I didn't want to muck up/embarrass myself too much by messing with our makefiles thoughsysimg.jl
, I'd just be able to dousing QuadGK
afterusing Base
, after modifyinginit_load_path
ininitdefs.jl
, butusing
didn't seem to be able to find theQuadGK.jl
file instdlib
. Is there a way to do that? Or is that only a package thing?