Summary: | [quick fix] Remove argument quick fix could guess which parameter to remove | ||
---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Benjamin Muskalla <b.muskalla> |
Component: | UI | Assignee: | JDT-UI-Inbox <jdt-ui-inbox> |
Status: | ASSIGNED --- | QA Contact: | |
Severity: | enhancement | ||
Priority: | P3 | CC: | daniel_megert, martinae |
Version: | 3.4 | ||
Target Milestone: | --- | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: |
Description
Benjamin Muskalla
2008-06-16 17:32:16 EDT
Nice to have, but how often does it happen that arguments are matching the parameter names? Is it worth the extra analysis? At least in the JDT source itself i stumbled across several places where this fits into the picture. One example is the DefaultProblem ctor which is often called where the arguments match the parameter names. In addition to the name matching mechanism as stated in comment #0 it could be implemented with the types in mind. package A; public class E { void foo() { String foo= ""; int param= 5; boolean bar= true; bar(foo, param, bar); <- invoke quick fix "Remove Argument" } private void bar(String foo, /* int param, */ boolean bar) { } } |