Summary: | [refactoring] Refactoring like “change method signature” for generic type and method type parameter lists | ||
---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Glenview Jeff <junk> |
Component: | UI | Assignee: | JDT-UI-Inbox <jdt-ui-inbox> |
Status: | ASSIGNED --- | QA Contact: | |
Severity: | enhancement | ||
Priority: | P3 | CC: | amj87.iitr, deepakazad, markus.kell.r, tom |
Version: | 3.8 | ||
Target Milestone: | --- | ||
Hardware: | PC | ||
OS: | Windows 7 | ||
Whiteboard: |
Description
Glenview Jeff
2012-02-25 09:39:43 EST
Moving to JDT/UI That would be interesting for types as well as for methods that have generic type parameters. Definitely for types as well, thanks for the idea! Actually I just realized after posting the reply that I don't actually know what you mean by it applying to "types" as a distinct concept from it applying to generic class parameters. Could you please explain the distinction? "type" is the general term for classes and interfaces (including enums and annotations). The feature should not only work for generic classes, but also for interfaces: public interface Map<K,V> {..} ... and for methods: public static <T> void copy(List<? super T> dest, List<? extends T> src) { .. } FYI, out of curiosity, I tested this out in IntelliJ IDEA and it works as described in this enhancement request. |