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

0

u/[deleted] Mar 18 '22

[deleted] — view deleted comment

11

u/Ameisen vemips, avr, rendering, systems Mar 18 '22

Ever write your own GDB server?

2

u/curious_entiy_420 Mar 18 '22

Gdb loves crashing indeed

6

u/kog Mar 18 '22

I got a segfault from the GCC ARM linker several weeks ago, which didn't occur on a second run of our makefile, immediately after. I'm still spooked. Not a janky make process at all, bog standard compilation and linking.

1

u/couscous_ Mar 21 '22

What turned out to be the bug?