is_set() tests fail with clang on windows

[emptywalls]

error: static_assert failed due to requirement '!brigand::is_set<int, int>::value' "error in brigand::is_set"
static_assert(!brigand::is_set<int, int>::value, "error in brigand::is_set");
^ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
error: static_assert failed due to requirement 'brigand::is_set<void, int &, int>::value' "error in brigand::is_set"
static_assert(brigand::is_set<void, int&, int>::value, "error in brigand::is_set");
^ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
error: static_assert failed due to requirement 'brigand::is_set<void, const int, int>::value' "error in brigand::is_set"
static_assert(brigand::is_set<void, const int, int>::value, "error in brigand::is_set");
^ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
error: static_assert failed due to requirement 'brigand::is_set<int, short, double>::value' "error in brigand::is_set"
static_assert(brigand::is_set<int, short, double>::value, "error in brigand::is_set");
^ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
error: static_assert failed due to requirement 'brigand::is_set<int, short, double, float>::value' "error in brigand::is_set"
static_assert(brigand::is_set<int, short, double, float>::value, "error in brigand::is_set");
^ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
error: static_assert failed due to requirement 'brigand::is_set<int, void, int &>::value' "error in brigand::is_set"
static_assert(brigand::is_set<int, void, int&>::value, "error in brigand::is_set");
^ ~~~~~~~~~~~~~~~~~~~~~~~~~~~

clang-cl.exe --version
clang version 7.0.0 (trunk 328716)

#define BRIGAND_COMP_MSVC fixes the problem.
In particular I have encountered this using chromiums build environment since they moved to clang on windows.

[edouarda]

It's clang on which platform?

[emptywalls]

clang-cl.exe --version
clang version 7.0.0 (trunk 328716)
Target: x86_64-pc-windows-msvc

[emptywalls]

Also as I already mentioned I encountered this in chromiums build environment which has a rather lengthy list of compiler switches applied. The error very well may be due to clangs compatibility to msvc, I have not looked closely.

[edouarda]

That may be the case as I think we only test Clang on Mac and Linux.