You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A limitation of the current API design is that both types used in the variant have to be different. The error is that the compiler will not be able to decide which of the "left" or "right" values to set when constructing the variant from some value.
I'm not intending to make further changes to this as a variant class has been added to the C++ standard library for C++17 (std::variant) and you can find polyfills for compilers that don't ship with it yet.
Oh, good grief. You're right. Maybe<T> uses Either<bool, T> in its definition. The definition ought to be something like Either<NothingType, T> where "NothingType" is an internal type that is only used to represent a missing value.
The text was updated successfully, but these errors were encountered: