-
Notifications
You must be signed in to change notification settings - Fork 915
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
Restructure JSON code to correctly reflect legacy/experimental status #13757
Restructure JSON code to correctly reflect legacy/experimental status #13757
Conversation
@@ -547,7 +543,7 @@ void convert_json_to_columns(parse_options_view const& opts, | |||
} | |||
|
|||
/** | |||
* @copydoc cudf::io::gpu::detect_data_types | |||
* @copydoc cudf::io::json::detail::legacy::detect_data_types |
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 namespace was incorrect here AFAICT
…vuule/cudf into fea-read_json-namespace-cleanup
@@ -33,7 +33,7 @@ namespace cudf::io::json::detail { | |||
* | |||
* @return cudf::table object that contains the array of cudf::column. | |||
*/ | |||
table_with_metadata read_json(std::vector<std::unique_ptr<cudf::io::datasource>>& sources, | |||
table_with_metadata read_json(host_span<std::unique_ptr<datasource>> sources, |
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.
Out of scope for this PR, but a host_span<unique_ptr>
feels off when it comes to ownership semantics. This pattern seems prevalent in cuIO though. Also I don't know if there's a nice idiomatic way to write this otherwise though since most implicit conversions won't quite work and there's limited interop between implicit conversions and template deduction.
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, really sends a mixed message :D
Surely we can lose the unique_ptr
s somewhere along the call chain...
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.
Why do we need this new header?
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.
Because we now call legacy::read_json
from read_json.cu
. It does make me wonder if we still need the other read_json.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.
Just checked, the other header is needed for tests; keeping the files as they are.
/merge |
Description
Closes #11982
Moved files to correct directories.
Updated namespaces: experimental -> base, base -> legacy
Improved namespace nesting to reduce the need for fully qualified names (
json::detail
instead ofdetail::json
).Use
host_span
instead ofstd::vector &
in allread_json
variants.Checklist