Request
Per discussion in #2337 it would be useful to have a standard set of errors we could use for result-style error handling for container-like objects that covers common errors like out-of-bounds access, invalid parameters during creation, etc. The reasoning being that there probably isn't much marginal utility in having each container-like class redefine errors for these common use cases, but having a set of our own error codes/error messages provided by ystdlib for these use-cases is better than relying on std::errc error codes that don't quite fit.
Possible implementation
Add a new error code + error code enum in a dedicated file in ystdlib.
Request
Per discussion in #2337 it would be useful to have a standard set of errors we could use for result-style error handling for container-like objects that covers common errors like out-of-bounds access, invalid parameters during creation, etc. The reasoning being that there probably isn't much marginal utility in having each container-like class redefine errors for these common use cases, but having a set of our own error codes/error messages provided by ystdlib for these use-cases is better than relying on
std::errcerror codes that don't quite fit.Possible implementation
Add a new error code + error code enum in a dedicated file in ystdlib.