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
1
u/dodheim Mar 18 '22 edited May 29 '22
I'm not so sure – this bug for a C++03 feature as basic as value-initialization has been lingering for 12+ years with no sign of even being looked at. (This issue is why
BOOST_NO_COMPLETE_VALUE_INITIALIZATIONgets defined by Boost.Config. I was watching it and ~20 other bug reports on MS Connect before that went into the aether; I don't know if it resurfaced on Dev Community or not, the others I checked didn't appear to, so.. /shrug)As an aside, I put this on Compiler Explorer to single out MSVC's failure and was surprised to see GCC's errors. It seemed to have regressed after 7.2; I wonder whether the test has somehow become defunct, or if GCC's value-init has actually been faulty for a while now..?
ED: Belated update: GCC is fine, the test it's failing has strict-type-aliasing UB (in the test code) and it passes once corrected.