Stop converting the "-std=c++0x" to "-std=c++11"

[ghuser404]

So I have this weird issue, my project is using gcc 4.6.3, and it looks like the compiler has a bug, that vscode rightfully gives an error about, but the code builds. It's a bit annoying and isn't cool overall. What can I do about this issue?

The bug is as follows:
I have a struct, let's say struct Foo { int id; std::unordered_set<int> set; };. My class has a private member of this struct, and it initializes it in initialization list like this : member({ 0, { } }).

The problem with this is that gcc 4.6.3 unordered_set default constructor is explicit, which is why member({ 0, { } }) gives an Intellisense error, according to C++11. However, if this was actually an invalid code, I would write member({ 0, std::unordered_set<int>{ } }) (which is subjectively less pretty), but standard actually says that unordered_set default constructor is not supposed to be explicit, and so my code builds correctly in later gcc versions.

Is my only option to either update gcc or to write ugly code just to satisfy IntelliSense?
Another option would be to ignore it, but let's not talk about this.

[sean-mcmanus]

gcc 4.6.3 appears to not fully support C++11 and only supports the c++0x flag -- is that what you're building with? If you run C/C++: Log Diagnostics with the source file active, what is reported as the "Standard Version"? I would update your compiler if possible (4.6.3 is very old). You could also try surrounding the code with #ifndef __INTELLISENSE__ to make code non-visible to IntelliSense.

The code I'm using is:

#include <unordered_set>
struct Foo
{
    int id;
    std::unordered_set<int> set;
};

class Bar
{
public:
    Bar(): member({ 0, { } }){}
private:
    Foo member;
};

It's possible our emulation of c++0x with that version of gcc is incorrect -- our parser tries to parse things the same depending on the version used.

Also, if you're using gnu versions see #2782 .

[ghuser404]

Yes, the project is using the c++0x flag.
C/C++: Log Diagnostics gives Standard Version: c++11.

It's possible our emulation of c++0x with that version of gcc is incorrect

Does cpptools actually take compiler version into account? If so, theoretically this could be possible to fix on the cpptools side?

our parser tries to parse things the same depending on the version used.

You mean, depending on the version [of c++ standard] used?

PS. I've actually been looking into updating the compiler, I wish it was easier than it actually is. We're building our toolchain with an old version of buildroot, and I've had some issues upgrading to a newer one. But we'll get there... eventually.

[sean-mcmanus]

Yes, our parser takes the gcc version into account. However, it looks like we are incorrectly sending our parser a c++11 flag instead of c++0x, which should be trivial for us to fix (not 100% sure that would fix your issue though, i.e. if our parser still doesn't handle it correclty).

[ghuser404]

Awesome! Let me know whenever an insider build contains this fix, I'll test it for you.

[sean-mcmanus]

Fixed with https://github.com/microsoft/vscode-cpptools/releases/tag/0.28.0-insiders .