¿My understanding is that part of the reason Contracts caused this kind of failure is that it was set up to be a change far too deep? Like, if something like going for std hardening requires Contracts, I can understand the fear that we might end up in yet another std::regex situation except for the entirely of std::. On my initial attempts to read the Contracts papers, it all felt like a LLM was let loose on the Standard, and at points made me think "what if they changed the properties of double?".
If it was designed to be decoupled so that Hardening does not depend on it, or if it was set up to be a partial implementation with an expectation to get completion across two Standards (so basically, "starts in 26, ends in 29" for example), could this have had a better result?
all 6 comments