Full covariance support for tuple types is awkward, because the underlying .NET Core tuple type is not covariant. However, we can support covariance when constructing tuple literals in a context where we know what element types are actually expected - for example in a return statement or expression function body, in an assignment statement or as a function actual argument.
Full covariance support for tuple types is awkward, because the underlying .NET Core tuple type is not covariant. However, we can support covariance when constructing tuple literals in a context where we know what element types are actually expected - for example in a return statement or expression function body, in an assignment statement or as a function actual argument.