Doug Kelkhoff

In the spirit of honing the scope of a few distinct crates, I'd like to explore decoupling the parsing from the evaluation a bit more consciously. This is _almost_ decoupled,...

This design would be more difficult to deal with using things like Rs `do.call` - specifically for `[` and `(` if they’re being repurposed as vector and list constructor syntax....

Would you consider using `class` in place of `type`? I know that’s a divergence from R, but I’m continually befuddled by Rs mismatched mode/class - especially for numerics - and...

Thankfully, for now this is definitely not an issue as we currently don't support `NaN`. This was intentional, as I'd like to keep the number of esoteric values rather minimal....

This does open up a question for whether mathematical operator commutative-ness should be enforced by the language. Enforcing that their commutative would mean that something like `ggplot2`, which (I think)...

> 0 / 0 > [1] NaN :eyes: How did that get in there! It's surely just the internal `f64`.. but I never realized it snuck in. I'd probably have...

> I am wondering though whether there was a specific reason why the `Names` subset was implemented via `NamedSubsets` Yeah, this part isn't as clean as I'd like. It could...

> One idea I had is whether we maybe want to add a `NamedSubsets` variant to the `RepType` enum. Let me make sure I'm understanding you correctly here. The proposal...

Assigning `NULL` as a way of removing elements is definitely odd. One way to address this would be to implement a version of `[.list` that operates on functions. Then you...

> Do you have a preference @dgkf. Probably I would tend to just make `[1, 2, 3]` create an integer and `[1.0, 2.0, 3.0]` a double Yeah - I'd prefer...