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
I wasn't precise enough in my comment there. As far as I can tell, the first case with string* is diagnosed because the "unmanaged constraint" on pointers is checked at the time C<string*[]> is bound--and we have a test for this. The second case however isn't caught because we check the type parameter's constraints after field types are bound.
As @cston pointed out (I think only offline?) there is a similar bug with method return types in 2.9.0 and today:
As observed by #34693 (comment) the following program fails to report the incorrect use of a pointer type after #34739
here is another case that isn't properly diagnosed:
The text was updated successfully, but these errors were encountered: