-
Notifications
You must be signed in to change notification settings - Fork 65
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
Fix default values for stream parameter #1583
Conversation
Signed-off-by: Nghia Truong <[email protected]>
build |
src/main/cpp/src/decimal_utils.hpp
Outdated
@@ -16,45 +16,39 @@ | |||
|
|||
#include <cudf/column/column_view.hpp> | |||
#include <cudf/table/table.hpp> | |||
#include <cudf/utilities/default_stream.hpp> | |||
|
|||
// |
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.
Comment with no text? Should either remove these or add a comment. I'm assuming this is to delineate sections of the includes (IMO not necessary, pretty obvious from include paths or lack thereof), but without text it's not clear what the intent is.
Applies to everywhere this was added in 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.
This is due to the issue with clang-format that messes up the header order. I have to use an empty comment line to prevent header reordering.
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.
Does it need to be empty, or can the comment say "// this is here to avoid clang-format from rearranging the header files". Also wondering why we're explicitly avoiding the recommended header order?
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.
The current clang-format config combines headers together and doesn't respect the conventional "near to far" order. That means we should include our header first, then library headers, then builtin headers. By using "near to far" order, we can ensure that most headers have their own dependencies included themselves.
We probably should change the config a little bit to account for that.
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.
Ideally if we switch to use .clang-format
style from cudf then we don't have to worry about this as cudf config can avoid this mixing header issue.
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 is another option: fix the style to preserve header grouping: #1584. With that, the header organization is totally up to the code author.
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 this looks good to me.
Signed-off-by: Nghia Truong <[email protected]>
Signed-off-by: Nghia Truong <[email protected]>
Signed-off-by: Nghia Truong <[email protected]>
This reverts commit 9b6b528. Signed-off-by: Nghia Truong <[email protected]>
This last commit was so much easer to read! 😸 |
build |
This changes the default values for stream parameter in various APIs. We should switch to use
cudf::get_default_stream()
which is consistent throughout the library (it will be eitherrmm::cuda_stream_default
orrmm::cuda_stream_per_thread
). Using onlyrmm::cuda_stream_default
may lead to mixed use ofrmm::cuda_stream_default
andrmm::cuda_stream_per_thread
in the same place.