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

Planning: core standard library #34

Open
LB-- opened this issue Nov 1, 2015 · 1 comment
Open

Planning: core standard library #34

LB-- opened this issue Nov 1, 2015 · 1 comment
Assignees
Labels

Comments

@LB--
Copy link
Member

LB-- commented Nov 1, 2015

I think the core library should be very minimal and provide only the basics needed to write the hello world program. More high level things like containers, filesystem access, etc. should be separate modules, also they are only downloaded and linked in as needed. This is intended to avoid huge library bloat that happens to so many libraries and even language standard libraries. It should be simple to use existing libraries, so much so that you shouldn't even notice a difference from using the core standard library.

@LB-- LB-- added the planning label Nov 1, 2015
@LB-- LB-- self-assigned this Nov 1, 2015
@LB--
Copy link
Member Author

LB-- commented Jul 13, 2016

Standard IO streams pose a problem. I don't want to make the mistake of baking in a bad standard stream implementation in the core standard library. Maybe those can just be really low-level structs and then if you want something better you can import the module of your choice and use an adaptor or something.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant