search

StardustPL / Stardust

"A programming language that doesn't make me angry to use it."
https://StardustPL.GitHub.IO/
The Unlicense
4 stars 0 forks source link

Planning: core standard library #34

Open LB-- opened 8 years ago

LB-- commented 8 years ago

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-- commented 8 years ago

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.