"This article was originally published in Polish in issue 4/2013" — a lot of excellent advice. Sad to see C++ have moved in last decade in a direction that makes writing efficient, simple low level code harder and harder :(
I think it has become EASIER: for instance, since C++23 Rust-like move semantics can be used, which provides the compiler with extra information that can be leveraged for the generation of better code.
Or take constexpr - it permits to move computations to compile time that are complex and in older versions either had to be done at runtime, or an ugly workaround had to be used (e.g. assigning a mysterious literal pre-computed in another run or by hand).
The closest thing I can think of is trivial relocation [0] which matches the bitwise copy + no destructor on moved-from bits of Rust's moves, but that was only added to the draft for C++26 and was removed late in the process anyways [1].
112233 · · focus · HN ↗
jll29 · · focus · HN ↗
Or take constexpr - it permits to move computations to compile time that are complex and in older versions either had to be done at runtime, or an ugly workaround had to be used (e.g. assigning a mysterious literal pre-computed in another run or by hand).
creata · · focus · HN ↗
What C++23 feature allows that?
aw1621107 · · focus · HN ↗
[0]: <a href="https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2025/p2786r13.html" rel="nofollow">https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2025/p27...
[1]: <a href="https://herbsutter.com/2025/11/10/trip-report-november-2025-iso-c-standards-meeting-kona-usa/" rel="nofollow">https://herbsutter.com/2025/11/10/trip-report-november-2025-...