Vyas Ramasubramani
Vyas Ramasubramani
I believe this was just a POC, so I'll close it since we can always view the PR later.
I would recommend that we not try to address this until we rework cudf internals around pylibcudf objects. At that time we'll be reconsidering underlying data structures anyway.
Closing as resolved. Please feel free to reopen if needed.
[Rich supports adding sections](https://rich.readthedocs.io/en/stable/tables.html#lines). If we're going to group all non-pandas calls into an "other" entry, can we add a line between that and all other rows so that there's...
I agree, I think if we're going to include the "other" data we have to be careful what UX we present so that it alleviates rather than increases confusion.
@Matt711 are you proposing that we close this issue, or do you think there are still ops that need to be updated?
This issue was originally opened because protected members need to be documented, as we discovered in #1317. That makes sense because if a class allows subclassing a consumer needs to...
xref: https://github.com/rapidsai/cudf/issues/18251
My fear with this kind of analysis is that I believe the compiler is free to reuse bits of rodata however it sees fit. A smart enough compiler could see...
I did a much more thorough analysis of exactly what went wrong in rapidsai/cudf#18251, see https://github.com/rapidsai/cudf/issues/18251#issuecomment-2725967075. tl;dr I think that my above concerns are definitely valid and any non-ELF-aware rewrite...