Value or Error

ValueOrError Concept

Something not really mentioned until now is how Outcome interoperates with the proposed std::expected<T, E>, whose design lands in between outcome::unchecked<T, E> and outcome::checked<T, E>, both of which are simplified aliases for outcome::result<T, E> hard coding the NoValuePolicy to a fixed policy. Expected and Outcome are isomorphic to one another in design intent, but interoperation for code using Expected and Outcome ought to be seamless thanks to the proposed ValueOrError concept framework, a subset of which Outcome implements. »