Am I wrong in thinking that this mild form of schizophrenia ( no official ABI but dont break the ABI) is part of the reason why we now live in a world where all applications talk to each-other through sockets, incurring huge overheads?
What is the "runtime overhead involved in passing unique_ptr by value"?
The reference is a 1h YouTube video.
Discussion of whether the next (or any future) c++ release should break abi compatibility.
C++ ABI issues seem to be in this paradoxical situation where the language standard powerbrokers simultaneously feel that
a. Having a real binary compatibility story is beneath C++, but
b. The accidental ABI compatibility that exists today is too widely adopted to break.