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
Thanks @peq. I wonder if it makes sense to implement destroy for native types with no-op, so that destroy is globally implemented trait. That would be a nice stop-gap before new generics
That would not help without new generics. With current generics, T is erased and there is just an int. So destroy would always be a no-op for generic types, which would be very confusing.
Is this something that new generics can help with?
The text was updated successfully, but these errors were encountered: