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
{{ message }}
This repository has been archived by the owner on Nov 1, 2020. It is now read-only.
B.f is protected and we shouldn't consider it as implementing the interface.
usingSystem;interfaceI{intf();}classA{publicintf(){Console.WriteLine("Correct -> Should be in A.f()");return100;}}classB:A,I{newprotectedvirtualintf(){Console.WriteLine("Incorrect -> Shouldnt be in B.f()");return1;}staticintMain(){Bb=newB();Ii=b;returni.f();}}
The text was updated successfully, but these errors were encountered:
MichalStrehovsky
changed the title
Method declaration order not respected in interface method resolution
Accessibility not respected by the interface resolution algorithm
Jan 18, 2018
Fixesdotnet/corert#1986 (yep, all the way to CoreRT repo).
We finally found an instance where this matters - in MAUI. Non-public methods never implement an interface by name+sig combo. We got the `ProtectedDerived` case in the newly added test wrong.
Fixesdotnet/corert#1986 (yep, all the way to CoreRT repo).
We finally found an instance where this matters - in MAUI. Non-public methods never implement an interface by name+sig combo. We got the `ProtectedDerived` case in the newly added test wrong.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
B.f
is protected and we shouldn't consider it as implementing the interface.The text was updated successfully, but these errors were encountered: