-
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
For the overload of replace in libcudf where input/target/repl are columns, there isn't a maxrepl arg. #15855
Comments
To provide more context, in Cython when you have fused types, the number of arguments stays constant, so you can't have the situation like in C++, where you have an overload with one less argument or something like that. |
Supporting this in libcudf never really made sense since it would be confusing to know where the max was applied. |
That makes sense, I think I misunderstood what replace did. Renaming this might help. Maybe that's just me though. |
The documentation provides an example on how it works |
Yep that sounds good to me. |
Renames the multi-target overload of `cudf::strings::replace()` to `cudf::strings::replace_multiple()`. This helps with some Cython issues involving fused types and overloaded functions with the same number of arguments. Reference: #15855 (comment) This change deprecates the old name to be removed in a future release. Also added some additional error unit tests. Closes #15855 Authors: - David Wendt (https://github.com/davidwendt) Approvers: - Shruti Shivakumar (https://github.com/shrshi) - Nghia Truong (https://github.com/ttnghia) - Vyas Ramasubramani (https://github.com/vyasr) URL: #15898
Thanks! |
For the overload of replace in libcudf where input/target/repl are columns, there isn't a maxrepl arg.
We should probably support this in libcudf replace (eventually), otherwise we'll have some weirdness in pylibcudf where we'll have to raise for maxrepl despite accepting it as an argument.
Originally posted by @lithomas1 in #15839 (comment)
The text was updated successfully, but these errors were encountered: