Skip to content

Conversation

miscco
Copy link
Contributor

@miscco miscco commented Apr 15, 2025

This might be a bit controversial because CCCL currently does not officially expose std::algorithms

On the other hand it lets us replace a ton of thrust algorithms that are much heavier than the std::ones, so that might be a win.

There are two I could not replace, thrust::sequence and thrust::copy_if with a second input range because there are no std equivalents.

Also we currently did not port sorting algorithms because those are ... difficult for device compilation

@miscco miscco requested a review from a team as a code owner April 15, 2025 09:17
@miscco miscco force-pushed the drop_sequential_algorithm branch from bfc9a82 to 1a35b05 Compare April 15, 2025 09:20
@seunghwak seunghwak added improvement Improvement / enhancement to an existing function non-breaking Non-breaking change labels Apr 15, 2025
@bdice
Copy link
Contributor

bdice commented May 14, 2025

@miscco I don't think RAPIDS should adopt CCCL algorithms until they are publicly exposed. Happy to discuss more offline.

@miscco
Copy link
Contributor Author

miscco commented May 14, 2025

yeah, I will investigate what we can do for the sorting algorithms

@BradReesWork BradReesWork added the DO NOT MERGE Hold off on merging; see PR for details label Jul 17, 2025
@BradReesWork BradReesWork marked this pull request as draft July 17, 2025 20:29
Copy link

copy-pr-bot bot commented Jul 17, 2025

Auto-sync is disabled for draft pull requests in this repository. Workflows must be run manually.

Contributors can view more details about this message here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

cuGraph DO NOT MERGE Hold off on merging; see PR for details improvement Improvement / enhancement to an existing function non-breaking Non-breaking change

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants