Community
Participate
Working Groups
In current Eclipse 4.12, the method auto suggestion behaves irrationally, and suggests entries with partial matches, despite there are perfect matches. E.g. 1. Type `map.put`, `map` being `java.util.Map` 2. First suggestions are `compute`, `computeIfAbsent`, `computeIfPresent` 3. Suggestion no. 4 is `put` 4. Following suggestions are `putAll`, `putIfAbsent` See https://twitter.com/seleniumnodes/status/1166393111402209280 Expected: I expect `put` being the first suggestion, followed by `putAll` and `putIfAbsent`. Partial matches (entered string just appears within the method should be sorted to the back). I’m quite sure older versions did better -- I just recently updated from 4.7 to 4.12
I don't see this in Eclipse 4.13 build I20190902-1800. Please try with a recently downloaded build in a new workspace. Are you using Code Recommenders? If so, uninstall that and check again. Also, reset all Java > Editor > Content Assist preferences to default and try.
I have one environment Eclipse IDE for Java Developers 2019-09 M2 (4.13.0M2) where consistently map.put is wrongly expanded to map.compute Looking into preferences I see Java Proposals (Tasked-Focused) Disabling this and enabling instead Java Proposals restores completion to sane behavior. Thx, Noopur, for reminding me. Not code recommenders but Mylyn is the culprit this time. Do we have an open bug against them??
(In reply to Stephan Herrmann from comment #2) > Not code recommenders but Mylyn is the > culprit this time. Do we have an open bug against them?? No, can you please report it to Mylyn?
Switching “Java Proposals (Tasked-Focused)” to “Java Proposals” did the trick for me. Many thanks! I didn’t have time yet to try the new build, sorry. More background and my 5 cents: This was a vanilla installation of Eclipse with a brand-new workspace and without any additional plugins. If the “Java Proposals (Tasked-Focused)” are the default, this might be off-putting for new users.
Thanks for the confirmation. Moving this to Mylyn.
*** This bug has been marked as a duplicate of bug 506804 ***