Guillaume Dalle
Guillaume Dalle
Yeah, and that package isn't in very good shape at the moment, so maybe just deleting the section from the Distributions.jl documentation would be best?
Yeah I'm trying to clean up that PR too but I'm not sure I will have time before this summer
For future reference, here is the PR in question: https://github.com/JuliaStats/ConjugatePriors.jl/pull/43
Essentially I have thousands of columns with categorical entries and lots (> 90%) of `missing` values, so I thought it might be useful. However, it turns out that sparse columns...
But I guess there must be a good reason why `deleteat!` is not implemented for sparse vectors? Would there be a performance penalty?
Yes I agree with both of you. I just thought it would be a nice-to-have in my case, since categorical arrays still store one integer per value no matter what...
Yes, let's start with @pdeffebach's suggestion to shake things up in the stdlib
My data points were generated by many semi-independent sub-systems, and not every sub-system logs the same columns, which means most columns are very sparse
Just stumbled upon this issue, and it speaks to me since I implemented my own `VectorPriorityQueue` to improve performance. Even without heap structure, just with basic pushing and popping, I...
I would put them in the docstring so that they can be displayed in the REPL