No mention of Reflection which was passed to the Core Working Group for wording review, or senders/receivers (on the library side) which was actually voted into the working paper.
Huh? There is no such alternation between new features and feature freeze releases. In fact, C++26 will very likely get reflection as a major new feature. In comparison, the biggest core language feature in C++23 was probably "deducting this (explicit object member functions)".
The only thing that keeps Contracts out of C++26 is that they might not be finished in time (they'll need to be handed over from Evolution to Core by the February 2025 meeting, and then make it through Core review during the summer 2025 meeting).
Depends on what semantic you want. Sure, if you use a unique_ptr member, you will get a deleted copy constructor/operator - I wouldn't consider that blowing up in my face.
And even the presented fix hurts my eyes. Should have used a unique_ptr or optional.
Yes, it's not Open Source, but I am not sure that's really relevant here. I see it more as a prototype implementation for something that could be standardised for C++.
The linked tweet links to the recording, but it has apparently also been uploaded to YouTube: https://youtu.be/5Q1awoAwBgQ
Also the location of known Wifi networks.
Embracing the GC
I never actually liked the GC in D as it didn't seem to fit in with the general direction of the language, and Walter Bright in D at 20: Hits and Misses says:
Miss: Emphasis on GC
There is also lowendspirit, but in both cases you have to be very careful what you buy - not everything that is advertised there will work as advertised or will work long-term
where they will double your monthly data limit for free when you comment your order number.
where they use you to spam the forum thread (for giving away something rarely anyone has any use for)
You mean, don't trust a flatpak uploaded by a random person, but if there are enough fake reviews, it can be trusted?