-
Notifications
You must be signed in to change notification settings - Fork 174
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
Make Core more modular #1392
Labels
Comments
Yeah, I agree it's often hard to import things selectively in a good way. Moving |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
--no-core
is great if you don't want to pull in anything from the standard library, however, because of interdependencies between files in core, you cannot pick and choose which modules to use easily.For example,
copy
is defined in the module/file for the corresponding type, butstr
for all types is defined in String. In order to load coreString
routines, then, one needs to load every module that hasstr
defined inString.carp
. Likewise,Array
definesfor
, which is needed byStaticArray
andControl
andArray
in turn requiresMaybe
.We should try to make the dependencies graph a bit simpler so that it's at least a little bit easier to use the core modules modularly.
The text was updated successfully, but these errors were encountered: