algorithm,memory,numeric: Improve thrust compatibility via ADL barriers #433
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The recently introduced custom
pair
implementation in #425 resulted in regressions when using thrust's algorithms that have also been implemented by us, e.g.thrust::copy(...)
. This is caused by ADL sincepair
now is a member of the stdgpu namespace rather than thrust as before. Use ADL barriers to ensure that calling any algorithm from thrust will not accidentally delegate to our implementation.Fixes #432