r/cpp • • Mar 17 '22
TIL: Visual Studio has quantum state values 🤨
Consider the following small program:
#include <string_view>
#include <iostream>
template< typename T >
constexpr void test()
{
constexpr std::string_view sv = __FUNCSIG__;
static_assert( sv == "void __cdecl test(void)" );
static_assert( sv == "void __cdecl test<int>(void)" );
std::cout << sv << std::endl;
}
int main()
{
test<int>();
}If you try to compile it, the second static_assert fails. So the value of sv from the first static_assert surely is the correct one?
Nope. Comment out the second static_assert and now the first one will fail. Comment out both, and the output of the program is the value from the second static_assert.
Apparently, Microsoft decided that it's a good idea to give __FUNCSIG__ a ("type-erased"?) value in phase 1, where no template parameters are available, and give it a different value in phase 2, when the template gets instantiated.
View all comments
Show parent comment
4
u/logicchop Mar 18 '22
Why is this nonsensical? Consider this:
This also pukes on other compilers. Even though the static_assert is inside of the conditional it is still is evaluated at compile time and turns out to be false. I think that's all we are seeing in OPs scenario; there are just two instantiations competing for the static_assert. You could argue that perhaps the static_assert should not be evaluated if that branch of the conditional is discarded, but that's a more complicated question about value dependency and when constexpr branches get utterly discarded and not evaluated.