DeedleFake
DeedleFake
> What it comes down to is, would you rather have _no_ iterators (for the foreseeable future) or ones which can't be "chained"? No iterators, definitely. I've done fine without...
> While I don't know what the overall plans are, if you're hoping for Go to follow the path of Java Streams or C# LINQ, you might be in for...
Well, I tried. If that's the decision then that's the decision. I'm disappointed, but I guess I'll just be satisfied with what I _do_ like about the current proposal, even...
Purposefully not evaluating them won't work. The only way to call a function in the language is to simply use it. If a function has no arguments, it will get...
May also want to move the creation of streams from arrays from the `stream` module to this one.
A few more: - [x] `concat`. Alternatively, just stick this in `+` in `std` along with string concatenation. - [x] ~`append`. Similar to `append()` in Go. Need to make sure...
Even more: - [ ] `streamReverse`. Streams the array from the last index to the first.
Waiting on #20.
Any other features this needs? Maybe an equivalent of `os.OpenFile`?
Here's one: Add an `FS FileSystem` global variable with `FileSystem` being something like ```go type FileSystem interface { Open(path string) (File, error) } type File interface { io.Reader io.Writer }...