Another interesting type introduced C++26. This should make it easier to deal with owning polymorphic types at runtime.

This is indeed a good way to reduce the code generated by templates.

Need to mind the memory layout of your structs to get good performance. Often overlooked but that also includes the padding.

Probably more than you think in this setup. And even more in C++ with the STL having years of smart tricks behind it.

It's about time that it got fixed... This was really a language defect.

Indeed it's a very good new type of maps in many cases. Again a good illustration that nowadays memory layout is often more important than algorithmic complexity.

Interesting exploration of how static and dynamic dispatchs work behind the scene in Rust. The chosen tradeoffs are different than in C++ and that's something to keep in mind.

Some more details about std::indirect. Honestly looking forward to having it widely available.

Interesting tool. Maybe more chances for C++ and Rust hybrids?

Another nice addition to the standard for dealing with embedded assets.

This is a bigger trap than it sounds. It is very easy to fall into it.

More signs of C++26 being an important new standard for reliability and safety.

Looks like a nice improvement over std::unique_ptr for managing pimpl indeed. Really interesting stuff coming in C++26.

C++23 gives us std::ranges::view::enumerate for this particular case now. Still, this is a good illustration of the (too) little used range-based for loop with initializer.

Still need some work I'd say but this is interesting research. Transpiling C++ to Rust is getting more accessible. It need some improvements on the optimisation side to be more generally usable.

Those improvements are welcome. I wish we'd see more std::format uses.

Looks like a good book. This review definitely tempts me.

Interesting take on why CVEs are reported differently for C/C++ and Rust libraries. The responsibility for API misuse is treated differently because the abilities to express contracts is treated differently.

This is really interesting stuff that C++26 brings.

Cold and harsh look at how the C++ standard library evolves. There's indeed a problem in the fact that nothing gets removed ever.