David Anthoff

My vote would be to just release 1.0.0 as is, so that we get the full richness of semver going forward, it just makes the life of downstream packages so...

Here is the [Query.jl](https://github.com/davidanthoff/Query.jl) way to do this: ````julia @from i in t0 begin @select {i.id, names=split(i.val,",")} into i @from j in i.names @select {i.id,newval=j} @collect IndexedTable end ````

This query is actually two queries chained, i.e. a ``@select ... into i`` concludes the first query, and then right away starts a new query on those results with ``i``...

I think this is fundamentally a transformation that corresponds to the [SelectMany](https://dzone.com/articles/selectmany-probably-the-most-p) query operation in LINQ, which the second ``@from`` clause in the Query.jl example is. I don't think this...

This should work smoothly by just loading [IterableTables.jl](https://github.com/davidanthoff/IterableTables.jl) and then doing something like this: ````julia using DataFrames, IndexedTables, IterableTables df = DataFrame( param = ["price","price","price","price","waterContent","waterContent"], item = ["banana","banana","apple","apple","banana", "apple"], region...

I'll fix the iterable tables integration story for the new style API here. Then this ````julia load("file.scv") |> table # or table(load("file.csv")) ```` should work. I've also been sitting on...

Ha, I just realized that this new ``NextTable`` is already an iterable table source, without any integration code, simply because it iterates named tuples! Very nice. So all of the...

The table traits extension I’ve mentioned will actually end up just passing the arrays from TextParse to tables directly without any iteration, so at that point it should add hardly...

I think that is the dreadful Cairo.jl problem... DataVoyager.jl has a dependency on VegaLite.jl, which has a dependency on Cairo.jl, and the Cairo.jl build situation is not good... You could...

Does ``using Cairo``, ``using Rsvg`` and ``using VegaLite`` work?