This project is read-only.


Rename fails to simplify nested inherited types on conflict


evil corner case issue

abstract class A {
    public class B : A {
        public abstract class C : B {
            public abstract class D : C {


        object x = new B.C.D.B();
        object y = new B();
Rename D to B, and the first ctor call will be shown as an unresolvable conflict, even though the second ctor call is unaffected.
(there is exactly one legal ctor in this code, so they definitely refer to the same ctor)


Pilchie wrote Jul 22, 2014 at 5:27 PM

We are okay with letting this one go. Do you have a compelling example of source code that motivates addressing this issue?