Takafumi Arakaki
Takafumi Arakaki
> I think they make things tricky in interactive code Isn't `@vlplot(p1 & p2 & p3, repeat=...)` as easy to type as `@vlplot(repeat=...) + p1 & p2 & p3`? But...
> and now we got rid of one level of parenthesis You can get rid of the parentheses when the operation is associative and that is _why_ you don't need...
> Then the question becomes whether it would be `df |> @vlplot(repeat=...) |> @vlplot()` or the other way around `df |> @vlplot() |> @vlplot(repeat...)`. OK, that's interesting. If we say...
By subplots you mean concat? Isn't `[...]` concise enough?
Can't they be supported by `... |> @vlmod(...)`?
I'm opposed to overload `=>` because it's a type ```julia julia> => Pair julia> (=>) isa Type true ``` I think `T(...) isa T` should always hold if `T isa...
(But thanks for augmenting the point on transparent API on top the JSON spec!)
Replying to https://github.com/queryverse/VegaLite.jl/pull/227#issuecomment-569450659 > > This made me wonder if it makes sense to use `Tuple{Any,NamedTuple}` for this. > > Hm, but that adds another level of parenthesis, and I'm...
Ah, yes, I forgot that.
IIUC you still convert the data to columns, right? https://github.com/queryverse/VegaLite.jl/blob/c66278ce2010462c3864f8dfd2264ed6a44c536a/src/spec_utils.jl#L48-L49 This does not seem to cover the representations such as iterator-of-rows or [`Transducers.eduction`](https://tkf.github.io/Transducers.jl/dev/manual/#Transducers.eduction). OK, the latter is probably used only...