Is is intended behavior to have min max defined?

[shangjiaxuan]

Including tbb.h and global_control.h will pull in min max preprocessors from windows headers. This will occlude std::min and std::max usage in later code, and needs #undef. Is the preprocessors intended behavior? (Some downstream libraries breaks compilation on windows because of this.)

[shangjiaxuan]

Related: https://github.com/jrmadsen/PTL/issues/32 Related: https://github.com/oneapi-src/oneTBB/pull/603

[shangjiaxuan]

Although not in included directly, enumerable_thread_specific.h seems to contain a #include <windows.h> not guarded by NOMINMAX, locations of the winapi header that contributed to this issue is unknown.

[phprus]

See previous issue and PR: https://github.com/oneapi-src/oneTBB/issues/573 https://github.com/oneapi-src/oneTBB/pull/576

[Alexandr-Konovalov]

Fixed in Add NOMINMAX before windows.h in enumerable_thread_specific.h

[Alexandr-Konovalov]

So, closed. Please reopen if the issue remains.