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.
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
Refactor contiguous_split API into contiguous_split.hpp #13186
Refactor contiguous_split API into contiguous_split.hpp #13186
Changes from 7 commits
fe4e1ca
1d03252
edfdb07
36b837c
055ad37
8f896f6
892d947
22cb00f
37da022
96f36d9
a03907c
5619bc0
6dca7c0
f0cbdfd
71d4645
d8dd746
cc24e58
7a495e8
17940a4
3722a80
777d9f9
5e1ed6b
aabf6a9
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
I see no reason to have this struct. It just wraps around a
std::vector<uint8_t>
so can we just usestd::vector<uint8_t>
directly?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.
Yeah I just moved this code, but I see the point. I'll push a commit to remove the struct in favor of a
using
, which means the rest of the code that wants to usemetadata
as a type can still do so.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.
I broke the python build with this. I think all I need to do is define the type using
ctypedef
, I am working on it.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.
I think you can just remove this type completely and fix the python side, such as removing
cdef struct metadata
, replacingmetadata
with justvector[uint8_t]
.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.
Should be handled now with d8dd746
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.
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.
Also, recommend to use
std::vector<std::byte>
instead.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.
@ttnghia you marked this as resolved, but I haven't pushed it. Do you want me stick with
uint8_t
? I have been making the change locally and the main thing is I have to change other files in java/python and other source files on the cpp side. If we are OK with the bigger diff, I can spend time on moving us to this.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.
Oh sorry, accidentally marked as resolved 😄 . Yes, please address this.
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.
I have tried this, but it doesn't seem
std::byte
is defined in cython:Looking at
stddef
in cython, I see they didn't exposed that type: https://github.com/cython/cython/blob/1aef71764cd50e4cd2f638eac8e69fff3ced2224/Cython/Includes/libc/stddef.pxdShould we leave as uint8_t? Or should I handle this differently? @ttnghia
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.
@ttnghia I did remove the typedef for
metadata
and went directly with thestd::vector<uint8_t>
here: d8dd746There 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.
Keeping
uint8_t
is fine. I want to move forward with a more standard way that libcudf devs prefer (std::byte
instead of other types) but understand that it is may be out of scope of this PR.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.
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.
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.
Typo?
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.
yeah this was not clear. I rewarded it (will push shortly)
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.
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.
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.
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.
Curious about
@param[in]
. In this case, it is inconsistently used (e.g.input
andsplits
should also be@param[in]
). The reason I bring this up is because I see lots of usage of@param[in]
in cuDF, and was wondering if this is going out of favor (being replaced by just@param
)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.
In general, we drop the
[in]
especially when all parameters are[in]
The
[out]
is relatively rare and should be used to clear up any ambiguity.https://github.com/rapidsai/cudf/blob/branch-23.06/cpp/doxygen/developer_guide/DOCUMENTATION.md#param
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.
That sounds reasonable
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.
Don't use period
.
inconsistently.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.
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.
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.
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.
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.
Similar to my comment above, just use
std::vector<uint8_t/std::byte>
directly.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.
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.
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.