Skip to content
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

bmerge() needs to handle mixed complex-(int,dbl,i64) joins explicitly #6627

Open
MichaelChirico opened this issue Nov 27, 2024 · 8 comments
Open
Assignees

Comments

@MichaelChirico
Copy link
Member

MichaelChirico commented Nov 27, 2024

Follow-up to #6603.

We have this comment that's currently incorrect:

# just integer and double left

That's because complex is an ORDERING_TYPE:

ORDERING_TYPES = c('logical', 'integer', 'double', 'complex', 'character')

At a glance, we should:

  1. Treat complex the same as double iff all(Im(x) == 0)
  2. Error if any(Im(x) != 0)

To facilitate spotting this kind of gap in the future, I made this:

Screenshot of table in the spreadsheet linked below

Spreadsheet: https://docs.google.com/spreadsheets/d/1RhNhXRA_5frgeqF9_ZS0Sll94RVs0iFgb5u7DBrgpaQ/edit?usp=sharing

@tdhock, what do you think would be a good place to keep this table as documentation? The joins vignette?

@tdhock
Copy link
Member

tdhock commented Nov 28, 2024

wow nice table!!! yes the joins vignette seems appropriate.
thanks for your detailed analysis, this is impressive.

@tdhock
Copy link
Member

tdhock commented Nov 28, 2024

the table is symmetric so maybe change the upper triangle to white/blank to emphasize that?

@MichaelChirico
Copy link
Member Author

MichaelChirico commented Nov 28, 2024 via email

@Abhishek2634
Copy link

Hii, @tdhock i would like to work on this issue, please assign me.

@venom1204
Copy link
Contributor

@MichaelChirico i guess changing the
mergetype () function would be enough, i mean adding the condition to check wheather the complex should be treated as double or rejected in the mergetype function would be enough for this .what you think

@MichaelChirico
Copy link
Member Author

MichaelChirico commented Jan 2, 2025

There is existing #6664 awaiting review, feel free to comment.

(FYI you can look at the comment thread and it will link existing issues/PRs that link back to this issue; also, the issue page will show the assignee)

@venom1204
Copy link
Contributor

hi
@Abhishek2634 are you still working on it? as it was assigned to you but no progress is done after the pr

@MichaelChirico
Copy link
Member Author

Abhishek is waiting for my review on #6664 as I understand it. Haven't gotten to it yet.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants