Isaac Deutsch

The libcu++ version is the one included with CUDA 11.2. cl.exe version: `Microsoft (R) C/C++ Optimizing Compiler Version 19.28.29336 for x64` nvcc.exe version: `Cuda compilation tools, release 11.2, V11.2.67`

Thanks for bringing awareness to that previous ticket. I've added a comment there.

Unfortunately, it doesn't work for all cases. We've found one such issue recently, see https://github.com/NVIDIA/libcudacxx/issues/131. In our project, we use quite a few templates for more flexibility between host &...

Here's a minimal example that causes compilation errors. Save as `.cu` or `.cpp` file, compile with `nvcc.exe` or `cl.exe` with the libcu++ includes. ``` #include struct A { float near;...

The libcu++ version is the one included with CUDA 11.2. cl.exe version: `Microsoft (R) C/C++ Optimizing Compiler Version 19.28.29336 for x64` nvcc.exe version: `Cuda compilation tools, release 11.2, V11.2.67`

:heavy_plus_sign: Also running into this limitation, preventing better performance. I'd really prefer a `k4a` device image type over an OpenCV one, though. Using an OpenCV type introduces a huge dependency,...

+1

Would `#undef`s for `near` and `far` after "windef.h" includes inside libcu++ not be a workable fix?