Quote:

‘unchecked’ std::errors are treated as ‘something which should never ever happen, but in practice MAY occur as a result of potentially-recoverable bug'

Another Quote:

Failing-Fast does NOT mean we should necessarily Fail-Hard(!). In certain (production!) cases, Failing-Fast-AND-Soft IS a substantially better alternative.

Quote:

having an ability to associate extra information with std::error is important for us – both for our own std::error exceptions, and for conversion from existing C++ exception

Another Quote:

I think that current C++ standard is Badly Lacking(tm) a concept of ‘segfault’ (which is supported by CPUs on VAST majority of modern systems with modern C++ compilers)

Quote:

No single error handling method is good enough for ALL the projects – which in turn leads to segmentation, with some of the projects using exceptions, and some others using error codes

Another Quote:

Right above I said that I like the std::error exception proposal a.k.a.[P0709R0]. However, as soon as I look at competing proposals, I begin to love it.

Quote:

We decide which set of types we’re using (fundamental or int*_t), and use it consistently

Another Quote:

The only thing we’re doing here, is changing the name of the type, NOT its behavior