You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Mar 21, 2024. It is now read-only.
NVIDIA/thrust#1688 made me think we should put this check directly into cuda::std::invoke_result.
#if defined(__NVCC__) && defined(__CUDACC_EXTENDED_LAMBDA__) && !defined(__CUDA_ARCH__)
static_assert(!__nv_is_extended_device_lambda_closure_type(F),
"Attempt to use an extended __device__ lambda in a context "
"that requires querying its return type. Use a named "
"function object or a __host__ __device__ lambda instead.");
)
#endif
This may be slightly controversial to put something in the cuda::std layer that is so CUDA (and nvcc) specific like this, but I don't see how it would harm anyone doing the right thing or not using nvcc.
The fact that it would help eliminate a lot of potential bugs outweighs any of the misgivings I'd have about adding this check.
The text was updated successfully, but these errors were encountered:
NVIDIA/thrust#1688 made me think we should put this check directly into
cuda::std::invoke_result
.This may be slightly controversial to put something in the
cuda::std
layer that is so CUDA (and nvcc) specific like this, but I don't see how it would harm anyone doing the right thing or not using nvcc.The fact that it would help eliminate a lot of potential bugs outweighs any of the misgivings I'd have about adding this check.
The text was updated successfully, but these errors were encountered: