Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Evaluate unification of how Thrust execution policies are passed around #3862

Open
Tracked by #101
jrhemstad opened this issue Feb 19, 2025 · 0 comments
Open
Tracked by #101

Evaluate unification of how Thrust execution policies are passed around #3862

jrhemstad opened this issue Feb 19, 2025 · 0 comments

Comments

@jrhemstad
Copy link
Collaborator

jrhemstad commented Feb 19, 2025 •
edited
Loading

@brycelelbach says that there's historical inconsistencies in how Thrust execution policies are passed around. With making breaking changes in 3.0, this could be a good time to evaluate moving to a more principled model.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
CCCL
Status: Todo
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jrhemstad