Community
Participate
Working Groups
Step 1: Create the class. public class A { public long k(long a) { return 10; } public long n(String a) { return 20; } } Step 2: apply the rename method to rename n to k. Eclipse will show a warning: Hierarchy declares a method k with the same number of parameters but different parameter type name. It would be nice if the tool could analyze wether the different parameter type represent a risk to behavioral preservation. In that case, for instance, we cannot have an implicit type conversion from string to long that could change a method invokation k(2) from k(long) to k(string). So the transformation is safe, we do not need a warning.
I think this warning can be annoying at times and should be removed in the described cases.