Skip to content

Make Core more modular #1392

@scolsen

Description

@scolsen

--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, but str for all types is defined in String. In order to load core String routines, then, one needs to load every module that has str defined in String.carp. Likewise, Array defines for, which is needed by StaticArray and Control and Array in turn requires Maybe.

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.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions