[jnwatson]

This is a great reminder of the pox that was Microsoft of the early part of the millennium. Besides an allergy to investing in web standards, they were woefully behind in their language support. Their non-adoption of modern C++ standards held client security back for a decade, and arguable held language standards development back.

[pjmlp]

There is a certain irony complaining about Microsoft, while praising everyone else in regards to C and C++ compilers, as if outside the beloved GCC, in a age where clang did not exist, the other proprietary compilers were an example of perfection.

Apparently the folks didn't learn their lesson with Web standards, given the power they gave Google to transform the Web into ChromeOS.

[chaboud]

That hardly seems fair.

(Microsoft was doing this to C++ well before the early part of the millennium…)

Edit: and in non-joke fairness, Microsoft has really come a long way on this regard.

[jinchengJL]

Having only worked with gcc and clang, OP’s code looked completely fine to me and I was baffled why many comments think the code is at fault. Judging by this page [1], I agree this is entirely MSVC’s doing.

[1] http://howardhinnant.github.io/container_summary.html

[Joker_vD]

Yeah, Microsoft absolutely should've made their containers use throwing move-constructors in violation of the standard, in order to better adhere to the standard.

In reality, it's a defect in the standard, plus a quality-of-implementation issue in the Microsoft's C++ Standard Library.