Description Marcel Bruch 2012-02-06 01:43:28 EST

Created attachment 210550 [details]
Screenshot showing completion on method arguments with emtpy prefix

When triggering code completion in method bodies w/o prefix, it proposes all locals, methods and fields visible at the current completion position:


void m(){
|<^Space> --> all visible locals, fields, methods are proposed



When triggering code completion on method arguments as in 

void m(){
  x.call(|<^Space)
}

it only shows the signature of the method you have chosen , and in the case x.call is an overloaded method all its variants, but not any visible local, field, or method. They are proposed only after the first character is typed:

String field;

void m(){
  x.call(f|<^Space) --> may propose "field"
}


From my observation, this behavior is confusing and additionally requires me to remember which variable or method I want to invoke from the early beginning. With this behavior code completion looses its function as a explorer for "what can I can do here?".

Since completions with empty prefixes are supported in other positions I wonder if  there is any reason why proposing variables and methods in method arguments shouldn't be proposed too with empty prefixes (probably below the list of methods I'm potentially going to use).


If there is no reason, I'd like to propose this as change for 3.8/4.2.