Prevent embedding of interfaces that contain non-abstract members. #34171
Conversation
AlekseyTs
added
the
Feature - Default Interface Impl
| Diagnostic(ErrorCode.ERR_DefaultInterfaceImplementationInNoPIAType, "ITest33").WithArguments("ITest33").WithLocation(6, 13) | ||
| ); | ||
| } | ||
| } |
There was a problem hiding this comment.
Would it be interesting to test this combination:
ITest33 with method declaration. ITest34 inerits ITest33, implements the method. UsePia test with both ITest33 and ITest34. #Resolved
There was a problem hiding this comment.
Would it be interesting to test this combination:
ITest33 with method declaration. ITest34 inerits ITest33, implements the method. UsePia test with both ITest33 and ITest34.
Added tests.
In reply to: 266136460 [](ancestors = 266136460)
|
|
||
| [ComImport()] | ||
| [Guid(""f9c2d51d-4f44-45f0-9eda-c9d599b58279"")] | ||
| public interface ITest33 |
There was a problem hiding this comment.
Is it worth testing an interface with a nested type (interface or abstract class), since they are new scenarios? Looks like we expect an error for that (ERR_NoPIANestedType). #Resolved
There was a problem hiding this comment.
Is it worth testing an interface with a nested type (interface or abstract class), since they are new scenarios? Looks like we expect an error for that (ERR_NoPIANestedType).
These are not new scenarios because VB supports types nested in interfaces. The ERR_NoPIANestedType is also covered in NoPia_06.
In reply to: 266158754 [](ancestors = 266158754)
No description provided.