-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
GH-37173: [C++][Go][Format] C-export/import Run-End Encoded Arrays #37174
Conversation
@felipecrv Should I make the equivalent Go side changes and push them to this PR/branch? Or should I make a separate PR? Thoughts? |
If you need my changes to test the Go implementation, you should wait a bit cause I'm still work on this one. I should even mark this as a draft. |
Unfortunately at the moment there isn't yet thorough c-data integration testing (but we want to add some). so I don't need your changes to add any testing, though I'd still want to do so manually at least. Do you have a preference for me keeping the Go changes separate from this PR or contributing it to this PR? |
Feel free to push to this PR. I think I'm done now with the changes after fixing the buffer count issues. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Mostly this looks great, just a couple nits:
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1, thank you @felipecrv
@felipecrv I've pushed the Go implementation for REE with c-export/import |
@zeroshade Would you like to add REE to the roundtripped types in |
@bkietz is out for now but it looks like both nits he had requested have been addressed. If there's no objections by tomorrow I'll merge this in. Thanks everyone! |
After merging your PR, Conbench analyzed the 5 benchmarking runs that have been run so far on merge-commit 9958896. There were no benchmark performance regressions. 🎉 The full Conbench report has more details. It also includes information about possible false positives for unstable benchmarks that are known to sometimes produce them. |
…ays (apache#37174) ### Rationale for this change All array types should be C-exportable. It uses `"+r"` as the format string. `+` because it's a nested format and `r` was not taken and seems like the obvious choice. ### What changes are included in this PR? - [x] Ability to C-import/expor REE arrays. - [x] Reference update ### Are these changes tested? Yes. * Closes: apache#37173 Lead-authored-by: Felipe Oliveira Carvalho <[email protected]> Co-authored-by: Matt Topol <[email protected]> Signed-off-by: Matt Topol <[email protected]>
Rationale for this change
All array types should be C-exportable.
It uses
"+r"
as the format string.+
because it's a nested format andr
was not taken and seems like the obvious choice.What changes are included in this PR?
Are these changes tested?
Yes.