Description Andreas Sewe 2017-06-22 05:25:51 EDT

The "Create enhanced 'for' loop" quick fix is ATM less smart than its "Assign statement to local variable" cousin.

A real life example:

  classHierarchy.getUnresolvedClasses();

    - Assign statement to local variable ->

  Set<TypeReference> unresolvedClasses = classHierarchy.getUnresolvedClasses();

This is great. But this could be better:

  classHierarchy.getUnresolvedClasses();

    - Create enhanced 'for' loop ->

  for (TypeReference typeReference : classHierarchy.getUnresolvedClasses()) {
  }

I realize, of course, that the latter requires some heuristics to convert the plural "UnresolvedClasses" into the singular "unresolvedClass", but covering 95% of the cases in English should be possible (just a gut feeling, though).