Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Catch ambiguous interface method resolution exceptions #15978
Is there a link anywhere that discusses implementation decisions? Seems like it would be good to have something written up, even if just an overview, in the CoreCLR design docs.
In particular I'm wondering if this is something that we could catch when the class is loaded, or whether that is too expensive and/or undesirable.
* The diamondshape test should work now that #15979 and #15978 are merged. * Create debug and retail version of diamondshape and sharedgenerics tests so that we have retail coverage. These tests hit issues around devirtualization (that is only active when RyuJIT is optimizing). * Add license headers