-
Notifications
You must be signed in to change notification settings - Fork 140
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow Any
type in column
#1027
Comments
This sounds similar to JuliaData/DataFrames.jl#3044 It seems DataFrames.jl users expect |
|
The point of this issue is that user originally had columns with |
i think On the suggestion for CSV.jl, i think right now the We do get to pick (and document) the meaning... but i slightly worry about providing a foot-gun, since if users expect the second meaning ("find me a concrete type What do you think? |
The docstring says:
So it promises column types. I agree this might not be the case, but then docstring should be clarified. I agree with your fears, and that is why I opened this issue to discuss what is best (in the end we might drop the original request and just fix the docs). |
I will propose something in DataFrames.jl |
Hmmm, yeah, this is tricky. One question is whether passing |
I imagined that PS. this is a low-priority issue |
having thought about it a bit longer, i'm coming round to the idea proposed here. That a non-concrete type |
That is why I was thinking of allowing |
oh, you mean special-casing |
Yes, as currently |
That's fine, I'll just make @nickrobinson251 do it 😛 . Yeah, I think I like special-casing |
Related to user's problem report https://discourse.julialang.org/t/help-with-appending-row-in-read-in-dataframe-weird-behavior/87734.
When you write:
you get an error. What can the user do to allow a flexible
eltype
for column read-in, likeAny
or e.g.Real
?The text was updated successfully, but these errors were encountered: