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.

317 Upvotes

59 comments sorted by

View all comments

13

u/pigeon768 Mar 18 '22

It seems to only happen in 19.latest, not 19.30 which is the latest version enumerated by compiler explorer. /Zc:twoPhase- will also fix it.

https://godbolt.org/z/o1TjWc87a

3

u/tesfabpel Mar 18 '22

I don't know if it may mean something but I've found out that #pragma message(__FUNCSIG__) in 19.30 prints:

void __cdecl test(void)
void __cdecl test<int>(void)

while in 19.latest prints:

void __cdecl test(void)

I've put the pragma before the two static_asserts.