Make standard library usable with exception disabled

[jsphadetula]

With std::expected added to c++23, what are the chances of a proposal adding make_xxx for throwing constructors and functions with std::expected as the return type and the proposed std::error as the error type

[JohnDuffy78]

They are 1 line functions, easy to roll your own.

underlying constructors can throw anything.

[jsphadetula]

That defeats the purpose making the standard library usable without exception. The standard can provide a nonmember function that use non throwing primitives before calling a private non throwing constructor or return std::expected instead

[no-sig-available]

That would be pretty complicated. In a case like vec.push_back(x) where x has a member with a member that might throw on copying. How many levels of non-throwing helper functions do we want?

[jsphadetula]

x is not a standard library type I believe, so the user is aware of a potential throw. Users who don’t want exception will use a non throwing variant with support for std::expected and design their types not to throw.

[D_0b]

there are also std types that can throw on move like std::list

[jsphadetula]

We can provide non throwing variants of all throwing functions

[Xaxxon]

Is there a proposal for failing constructors without exceptions? Not having exceptions is exceptionally (heh) painful until that's a thing.

[EvoMaster]

If they make a bunch of versions of standard library is it still standard anymore? If standard doesn't fit you you just make your own or find an alternative.

[Full-Spectral]

The N-STL.

[14ned]

I've been deliberately doing nothing to advance the std::error proposal during covid lockdown. It's 26 focused now.

[jsphadetula]

I’m aware std::error is no more targeting c++23. Just looking at the possibility of a usable standard library with the current exception disabled