piling up and its complexity grows to a ridiculous degree with every half-solution. I wouldn't be surprised to see C++'s usage fall off a cliff because the basic problem is its barrier to entry is too high.

I haven't used C++ nearly as long as some but I'm already really tired of this awkward ABI dog and pony show. We know why the competitor languages exist: primarily to fix issues in C++ that could very well just be addressed in C++ instead. There's a lot of smart people inside (and outside) the C++ community. For our own sanity, I really think it's well past time to put together a team of people to address this instead of giving us reflect_only_function. At least some of these problems are quite down to the fact that many things that, in my opinion, should have been language features were instead of implemented as library features. vector<bool> could long have been addressed if it wasn't in a header.

I'd love to help solve this problem, but I'm only one person and I'm by no means a C++ expert (given the famously high skill ceiling of C++) but it affects my day to day. I really wish C++ could actually start picking things off its wish list instead of continually punching itself in the face (see 8-point list above). I'm not going to list what I think C++ should do with an ABI break because not only can we not agree on breaking ABI, we can't agree on how to consistently name things. I don't know what the solution there is but I do constantly wonder if awkward naming could also be fundamentally solved by allowing ABI breaks. Maybe then we wouldn't have "copyable_function" because it would just be "function".

https://redd.it/1s766z8
@r_cpp