Use clang-cl driver by default about clang-power-tools

[zjturner]

Yea, definitely understand about wanting to be more conformant.

This is probably reasonable, the main thing I was concerned about is that people wouldn't be able to use it without going and learning a bunch of clang flags, which might be offputting for someone who wants an out-of-the-box experience that just works immediately after installing. As long as it "just works" with reasonable defaults then I'm happy :)

[cpp-red-lion]

Very informative feedback. Thanks, Zachary.
Will definitely consider clang-cl.exe driver as an alternative for the VS extension, in a future version.

We were reluctant to use the clang-cl.exe driver because it is too compatible with cl.exe, emulating its bad behaviors in terms of ISO C++ conformance (by automatically suppressing too many warnings).
We wanted to retain full control over the clang error flags, so that we can gradually eliminate all non-standard source code constructs. While this was annoying at first (lots of warnings), we found great benefits from actually fixing those warnings, instead of suppressing them.

I do agree, however, that for some teams this could be very challenging and a more cl.exe compatible option should be required. For this purpose, we now default to the following clang++ flags:

• -std=c++14
• -Wall
• -fms-compatibility-version=19.10
• -fms-compatibility
• -Wmicrosoft
• -Wno-invalid-token-paste
• -Wno-unknown-pragmas
• -Wno-unused-variable
• -Wno-unused-value

[Enache-Ionut]

How this issue is solved I will close it now.

Thank you for taking the time and helping us make a better product.