David Anthoff
David Anthoff
I think the definition for ``==`` in DataValues.jl is ok at this point. I'm also in the process of adding a ``DataValueArray`` that also fixes this, and then I'm also...
@nalimilan I also have a a branch on CategoricalArrays that uses DataValue. I almost feel the best way to handle that would be to just move that stuff into DataValues.jl...
> As for the future of DataTables, I think we'll have to discuss that with all involved parties. Yep, totally agreed. Who should weigh in on that? Maybe we can...
Bump. Ideally (from my point of view) we would move this repo over to https://github.com/queryverse and I would take over maintenance of it. Could we just move ahead with that,...
I'd like to revisit this. We plan to make a ``DataTable`` type a central piece for the Queryverse story going forward. We will use the name ``DataTable`` for the type,...
We want to do a fair bit of ``DataValue`` specific stuff, and my understanding is that DataFrames.jl doesn't want to take that dependency, nor adopt that approach.
We want to do things beyond just storing ``DataValueVector`` in a ``DataFrame``. The things we plan to do require DataValue specific code in lots of places where I think it...
Both have this: ````julia StatsBase.describe(nv::AbstractArray) = describe(STDOUT, nv) ```` That is the first of three overwriting messages I'm getting.
And then there is: ````julia function StatsBase.describe{T
Well, they actually contain code that is ``Nullable`` and ``DataArray`` specific :) So I guess they really should dispatch on fewer types?