windef.h include via windows.h include causes issue with "near" and "far" names about libcudacxx HOT 5 CLOSED

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 <cuda/std/atomic>

struct A {
  float near;
  float far;
};

int main() { }

from libcudacxx.

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

from libcudacxx.

Unfortunately there is nothing we can do here.

from libcudacxx.

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

from libcudacxx.

We cannot #undef macros from a system header.

While at the moment the macro might be useless it could get some meaning in the future leading to havoc

from libcudacxx.