Yeah, C++ is only a side actor on Apple since Mac OS got replaces with NeXTSTEP, Copland was C++ based, and BeOS as well, but Objective-C won.
Now with Swift, and the whole security legistation ongoing issues across several countries, Apple seems to only care to the extent it needs for their uses of LLVM, Metal Shading Language (C++14 dialect), and IO / Driver Kit frameworks.
They aren't contributing to clang as they once were, Google also not after the whole ABI break discussion.
On Windows land, it isn't much better, it appears that after getting first place reaching C++20 compliance, Microsoft decided to invest their programming language budgets on .NET, Rust and Go, asking the community what features that actually care about in newer standards.
Now with Swift, and the whole security legistation ongoing issues across several countries, Apple seems to only care to the extent it needs for their uses of LLVM, Metal Shading Language (C++14 dialect), and IO / Driver Kit frameworks.
They aren't contributing to clang as they once were, Google also not after the whole ABI break discussion.
On Windows land, it isn't much better, it appears that after getting first place reaching C++20 compliance, Microsoft decided to invest their programming language budgets on .NET, Rust and Go, asking the community what features that actually care about in newer standards.
https://developercommunity.visualstudio.com/t/Implement-C23-...
https://developercommunity.visualstudio.com/t/Implement-C26-...
So it is going to be hard going forward, expecting the very latest features on the three major compilers, when the contributions get reduced.