Stephan T. Lavavej

Yeah, we can do that once one or more maintainers are available. From memory, the work we accumulated and will need to port is: * Complete overhaul of our threading...

We'll be able to use concepts in C++20 mode, but not in C++14/17 mode - i.e. it's not like `if constexpr` or `explicit(bool)`.

@TheStormN Unfortunately, while we originally hoped that we could finish C++20 and switch to vNext, the compiler front-end team is currently too busy to work on vNext changes. :crying_cat_face: While...

@jonwil Long ago, we originally hoped that vNext would be ready for production at the same time as 17.0, but then it became clear that finishing C++20 was going to...

Comments from the MS-internal bugs (which may or may not be correct, especially mine :joy_cat:): @BillyONeal > As far as I can tell, this is completely conforming behavior. There is...

Nothing passes `_Nocreate` so we should remove it in vNext and investigate the other questions here.

@amyw-msft's analysis in Microsoft-internal VSO-275515, edited for clarity: > So there's three things here. > > One is that the standard behavior for `tellg()` is actually to discard `ungetc()` changes....

No updates, sorry. They keep finding more work for us (UCRT/STL maintainers) to do without adding more maintainers.

> Do you know if the above analysis regarding no standard way to convert full Unicode to multibyte is correct? I'm not deeply familiar with that part of the Standard....

No, they aren't set up to accept external contributions.