-
Notifications
You must be signed in to change notification settings - Fork 62
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
Audit use of _promote_op
#131
Comments
Two relevant links:
|
Related to your second point is a behavior in |
1 similar comment
Related to your second point is a behavior in |
There's one more remark. Issue #110 is also probably caused by this. In general I think a drawback of the current design is that it's difficult to use For these cases ( |
This is basically fixed in IndexedTables (after JuliaData/IndexedTables.jl#226 is merged). There are still a couple of uses in JuliaDB though:
But I don't know the distributed code well enough to know if it's feasible to remove those. |
Closing as now |
Very nice work @piever! |
Yeah, amazing amounts of deft work! 👏 |
This has served us well so far, but increasingly there is frustration when you end up with a table of a single Any column. We need to use the
Base.map
trick as much as possible.The text was updated successfully, but these errors were encountered: