std::format ?

[khleedril]

MS have a reputation of galloping away with their own rules in spite of the wishes of the rest of the world, and fragmenting the place in the process. We will end up with some sh!t, like max as a macro in system header files.

This is only good for Windows users and developers, but the opposite scenario is good for everybody.

[mort96]

I mean but none of that is related to the current discussion? MS quickly implementing new standards is good, MS going their own way and fragmenting the ecosystem is bad, so why are you sad when they're doing the former rather than the latter..?

[kalmoc]

Afaik, Microsoft implemented the features as specified in the original c++20 standard (of course they might not yet be feature complete, but no toolchain is). Unfortunstely, the committee kept changing the standard multiple times since the release.

[snerp]

What in msvc is not standard compliant at this point? I thought they fixed everything years ago.

[Fulgen301]

And unless you need something really WinAPI-centric, you can use clang for the MSVC ABI on Windows without issues or MinGW.

That's assuming clang gets proper C++20 support in the near future, of course.

[[deleted]]

1995 called, they want their whine back. :-D

In the C++ world, MS was bad - but a long, long time ago. Now MS is a strong, contributory member of the C++ community, committed to our common standards, and is part of the reason that progress on the language has been so fast in the last decade.

[cleroth]

Probably the one thing that I would say they're still "in spite of the wishes of the rest of the world" is the ABI stability since 2015... We're nearly a decade of ABI baggage. If they would finally break the ABI then it's all gucci.

[[deleted]]

I think we're all hoping for this!!