VS 2017

[SylvainCorlay]

Please check if your PR fulfills these requirements

• The title and the commit message(s) are descriptive
• Small commits made to fix your PR have been squashed to avoid history pollution
• Tests have been added for new features or bug fixes
• API of new functions and classes are documented
• If you PR introduces backward incompatible changes, update the version number
  in include/xtl/xtl_config.hpp according to the following rules:
  • if XTL_VERSION_PATCH is already 0-dev, you have nothing to do
  • otherwise, set XTL_VERSION_PATCH to 0-dev and increase XTL_VERSION_MINOR by 1

[SylvainCorlay]

@JohanMabille it seems that you fixed that issue earlier. I am not 100% sure I understand what is going on.

Moving to MSVC 2017 on appveyor fixes it, but not for clang-cl on azure.

The same issue is also coming up on xwidgets.

This may be due to the VS2017 migration of conda-forge. gtest was recently rebuild and the latest build may be using VS2017.