Tim Whiting
I think the alternative approach actually is a good design for long-term. We can be more consistent with errors, and provide succinct error codes, along with more descriptive messages.
The sample code here: Using `|-|` for spaces `|.|` for direct appending, `\` for newline and `\-` for newline + indent. ``` import std/core/stringb import std/num/float64 fun sb(l: list) match...
Closing, not priority right now, moving to community libraries for further use and experimentation.
By the way #525 improves memory usage and computation time a lot. Hopefully we can get the merged and released soon!
Good question. I do have an implementation already in one of my repositories somewhere. However, the lexer could be improved I think, currently it is slow. I have a version...
No space between -i and the path
Yeah, I think it is unfortunate, but I wonder if we can have a better help message potentially - if the file arguments are folders or something?
I think Daan has mentioned that he'd like the core c libraries to be minimal, so that we can create really small binaries. However, I agree that in most cases...
We might want to add a few more apis (cutting an array short and dropping the the rest of the array), or extending an array.
> > We might want to add a few more apis (cutting an array short and dropping the the rest of the array), or extending an array. > > Yes,...