DeedleFake
DeedleFake
Depending on how this works out, this might remove the need for a separate grammar for parsing standalone expressions, which could, in turn, remove the Go 1.9 requirement.
This will likely become basically unecessary once #53 is done.
Possible solution: Make arrays evaluate their elements when evaluated, returning an array of the evaluated elements. A quick test showed that this solves both problems. The big issue is that...
A feature that could be useful along with this that needs some planning is the ability to pass an existing array as the variadic list. This might require a new...
Might want to replace #33 with this one. Either way, though, waiting on gopherjs/gopherjs#705 as well.
The issue is that sets have to be immutable in order to fit with the functional programing setup properly. There are two primary ways to implement them in a way...
Alternative: Put an `at` function directly in `std` which can access indices of both strings and arrays. Not having to import it would be a bit easier, although it's potentially...
After a bit more experimenting, it might not make sense to use just `Text('f', -1)`. I'd like it to round large numbers of decimals but display large integers cleanly. I'm...
While I'd like numbers to just be `float64`s to make usage of them a bit easier from the Go side, I'd also kind of like to somehow make `Number` capable...
After attempting to implement the first variant (`{arg1 func arg2}`), I have discovered a problem that affects both. The usage of `{` at the beginning of an expression introduces an...