[libcu++] Correctly handle extended lambda in cuda::launch #6987
+111
−68
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.
There is no way to inspect arguments of an extended lambda in the host code, so we can't automatically dispatch to either pass the kernel config into the lambda or not.
For now the safe option is to require the user to explicitly pass in the config twice, which is not ideal, but lambda kernels are expected to be short and might not need the config object.
Added a test for extended lambda, had to move to lit test to be able to specify the nvcc flag.
This PR also changes some of the common testing headers, because I wanted to use the pinned type in lit test without including the c2h headers.