> it seems more likely that it isn’t actually the dealbreaker.
What is the dealbreaker then?
What is the dealbreaker then?
For example, I think it was bordering on malpractice for lambdas to ship without anything resembling a borrow checker in place. With lambdas that borrow from the stack, introducing memory safety bugs is shockingly trivial.
Even if your codebase bans lambdas in C++, it's quite reasonable to not fully trust the teams which made the decision to ship them.