feat: upcast schemas during set ops #10727
Open
+158
−53
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
NickCrews
force-pushed
the
set-ops-unified-schema
branch
3 times, most recently
from
7b2d8fc to
25413f7
Compare
NickCrews
force-pushed
the
set-ops-unified-schema
branch
from
25413f7 to
331145b
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
if I have a
stringand a!stringcolumn, they should be able to be combined. Same thing withint8andint16columns. I think this is what the underlying backends do already.I don't THINK there are any footguns lurking in here?
Related:
highest_precedence(*dtypes)#9335