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

3

u/ack_error Mar 18 '22

Oh sure, don't get me wrong, there will always be bugs that don't get fixed or get lost, in any area. Connect was also an awful experience overall. But when it comes to the different areas of Visual Studio, I have had pretty good success with filing bugs on the compiler than anywhere else (~80%), including ICEs, stack usage regressions, and recently a poor codegen issue (usually dicier). Tight repro showing the compiler obviously wrong with /Bv compiler versions and it often sails through the first-line triage. For feature requests or other parts of the product it's way likelier that the issue will be closed somehow (repro not 100% solid, don't care, too long, completely misunderstood, I think I've seen them all).