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
voidFoo<T>()whereT: unmanaged =>thrownewNotImplementedException();// This errors because it doesn't know that (int, int) is unmanaged.Foo<(int,int)>();
I would like the above to work.
I am specifically focused on tuples in my use case, but more generally I would propose that unmanaged should be checked after resolving generics. Currently it seems that all generic structs are rejected by unmanaged. I propose that a generic struct should only be rejected when, after generic resolution, it has a field of a managed type.
I would like the above to work.
I am specifically focused on tuples in my use case, but more generally I would propose that
unmanaged
should be checked after resolving generics. Currently it seems that all generic structs are rejected byunmanaged
. I propose that a generic struct should only be rejected when, after generic resolution, it has a field of a managed type.IntWrapper
can be used with theunmanaged
constraint.GenericWrapper<int>
cannot. I propose that it should be able to be.The text was updated successfully, but these errors were encountered: