Jacob Quinn
Jacob Quinn
Has anyone tried investigating this issue on [this PR](https://github.com/JuliaLang/julia/pull/42286)? It'd be interesting if that provides any additional insight (cc: @NHDaly , @vilterp)
Could be nice to lower `_` as a function argument to `@nospecialize(_)`
David and I didn't get a chance to talk about it at JuliaCon, which we had planned. The reality though, is that Tables.jl is already a superset of TableTraits.jl in...
I think David's comment from last year is still accurate and the best way forward: > Yeah, I think if Gadfly would simply use either Tables.rows or Tables.columns Tables.jl will...
On point 4., note that the Tables.jl interface is a superset of the iterable tables set of sources/sinks. I.e. any iterable table is also a Tables.jl-compatible source. This change was...
@ablaom, let me clarify. Every object `X` that implements/satisfies `TableTraits.isiterabletable(X)`, also automatically implements/satisfies the Tables.jl interface. This is because Tables.jl checks if an object first implements Tables.jl itself; if not,...
I would also agree that having the left data be dominant makes sense. It's the table for which you're keeping all keys (+ rows) and the joining table is "additional",...
I'm in favor of rule 1. I agree that keeping things simpler/more predictable for users will have the most benefit long term. And we can always tweak a case or...
Why not DataAPI.jl? It seems like it would be fine there.