Stephan T. Lavavej

We talked about this at the weekly maintainer meeting; we like `_STATIC_CALL_OPERATOR` and want to use `_CONST_CALL_OPERATOR` because it puts the keyword first and the context second, which is pleasingly...

Related to #1364. That issue is vNext because C++20 is locked down, but we can do whatever we want for C++23 until `/std:c++23` is finalized. Avoiding the tail-padding-reuse problem is...

Yes, thank you (especially for the fully reduced repro). I've added it to the list and tagged the internal bug as "STL-requested"; it is already assigned to our `/clr` compiler...

Thank you! :heart_eyes_cat: Apologies for the (somewhat holiday-related) delay in getting this reviewed. I've pushed a conflict-free merge with `main`, followed by changes to address previous feedback, followed by changes...

I'm mirroring this to the MSVC-internal repo - please notify me if any further changes are pushed.

Thanks for optimizing this important function, and congratulations on your first microsoft/STL commit! :rocket: :heart_eyes_cat: :tada: This is expected to ship in VS 2022 17.10 Preview 2.

Thanks, I've linked the Microsoft-internal bug to this issue. This is a rare example of a `vNext` bug where the bincompat break isn't nearly as bad as the source-compat break...

After thinking about this again, I suspect that this is not actually ABI-breaking, but the source-breaking change is indeed severe and I still don't know how to logistically go about...

It would still be a lot of work to clean up RWC but `/permissive-` does feel right for this. (I see how we could use our hack to apply noexcept...

We talked about this at the weekly maintainer meeting, and we're all in favor of deprecating `` (with an escape hatch as usual). @AlexGuteniev's suggestion of deprecating each publicly visible...