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
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: