This is a well-written and quite diplomatic summary by Herb Sutter. I'm not plugged in enough to be sure he's correct that Stroustrup's opposition was the main reason the C++26 vote failed where others have passed, but it sounds plausible.

It also lists 6 possible paths forward for C++26 with pros and cons. I think they are roughly:

A. Skip an official C++26 standard but roll these features into C++29.

B. Remove contracts from C++26 and pass it.

C. Say "please" and vote again.

D. Tweak contracts regarding virtual functions and vote again.

E. Pass C++26 as many different countries' national standards rather than an international standard.

F. Do E and also consider leaving ISO and moving to ANSI/INCITS instead.

I think "guaranteed contract enforcement" should be added to item D since that is explicitly called out as the only technical proposal that would change some NB votes from no to yes.