I was thinking of a case like this:
public class RenameTest {
public string AMethod(object x) {
return "AMethod has arg " + x.ToString();
}
public string aMethod(string s) {
return "aMethod has string arg \"" + s + "\"";
}
public static void RNMain(string arg) {
RenameTest rnObj = new RenameTest();
Console.Out.WriteLine(rnObj.AMethod(arg)); // *******
}
}
After renaming then the starred line will call a different method because of the more specific overload.
As you say this can happen already with properties and setXXXXX methods. We will look into adding warnings if we detect this might happen.
I was thinking of a case like this:
public class RenameTest {
}
After renaming then the starred line will call a different method because of the more specific overload.
As you say this can happen already with properties and setXXXXX methods. We will look into adding warnings if we detect this might happen.