You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- I see no mention of this fact other than perhaps indirectly (i.e. conclude this from the fact that rows are passed to the function rather than columns).
I assume this is still correct due to e.g. type stability as well as the performance of unpacing rows vs accessing the column vectors directly? Would you confirm please? And, do you think it would be prudent to state this explicitly?
The text was updated successfully, but these errors were encountered:
Yes, the reason is that DataFrameRow is not type stable. This info can be added to a docstring. Would you be willing to make a PR (I can do it instead)
Hello,
Thanks for your work on this package!
I happened to come upon your comment in the julia forums regarding performance of filter on whole dataframes vs column selectors;
https://discourse.julialang.org/t/adding-multiple-new-columns-to-dataframe/50997/14
Having read the documentation for
filter
both in installed versions and on the docs site - and now also the docstrings directly in the codeDataFrames.jl/src/abstractdataframe/abstractdataframe.jl
Line 1124 in 52d5a62
I assume this is still correct due to e.g. type stability as well as the performance of unpacing rows vs accessing the column vectors directly? Would you confirm please? And, do you think it would be prudent to state this explicitly?
The text was updated successfully, but these errors were encountered: