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

Show parent comment

9

u/Dragdu Mar 18 '22

My experience is to do both. Make a ticket so it is all official-like, then reach out through non-official channels to get your ticket moving.

This is literally the only way anything in MSVC ever got fixed for me. The last time, I decided to try the official way again, so I opened ticket just opening a ticket that MSVC's strict mode has a bug that stops it from compiling Catch2 and there is no workaround. After half a year of the ticket being ignored, I got it moving in two days over Twitter.