The latest Intel 2019 Update 5 compiler is not compatible with the updated Visual Studio 2019 16.4 headers.
C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\VC\Tools\MSVC\14.24.28314\include\utility(92): error: expected an identifier
!_Is_implicitly_default_constructible<_Uty1>::value || !_Is_implicitly_default_constructible<_Uty2>::value)
And so on with many other errors.
Since we aren't able to test a VS2019 version that released after the compiler release, you could run into some issues. Please use the VS2019 version prior to the compiler released date or wait for the next compiler version.
I know it's a moving target for Intel but MS agressively pushes updates. And given that MS does provide previews of upcoming versions it would be a good idea for Intel to be on top of these issues with possible work-arounds.
I can confirm this. Just updated to VS2019 16.4.0 and this breaks integration with Intel C++ 19.0 on Windows, as the OP eloquently point out. Telling an end user to "please use the VS2019 version prior to the compiler released date... etc." is not possible for any programmer also using VS2019, since you are telling an end-user never to install any of the VS2019 upgrades which Microsoft automatically provides via the Visual Studio Installer product. Instead Intel C++ on Windows should either:
1) Disable integration with the latest Visual Studio backend from Microsoft, and only allow integration with a prior Visual Studio release, where fixes are much less likely to break integration.
2) Issue update(s) to the latest Intel C++ 19.0 on Windows which reintegrate it with changes to the latest Visual Studio.
Just as no end-user would not want to have to refuse an update to the latest Intel C++ release, no end-user would want to have to refuse an update to the latest Visual Studio release.
Luckily for me since I also have the previous VS2017 installed, and I am using Intel C++ on Windows from the command line in testing Boost libraries, so I can change the compatibility in Intel C++ 19.0 on Windows from VS2019 to VS2017 and everything continues to work as expected. But I am sure not everyone is as lucky.
There is a workaround for this issue. Essentially it is MS fault for not recognizing the existence of the intel compiler.
please check out...