eclipse-jdt / eclipse-jdt/eclipse.jdt.ui
Content Assist with Java Type Proposals Sometimes Populates Slowly
- Dominant language
- Java
- Stars
- 59
- Forks
- 127
- Avg merge
- 23h 30m
- Merged PRs (30d)
- 35
Description
**Problem**
Eclipse Content Assist with Java Type Proposals is sometimes slow to populate. I can rapidly type 15 characters before any proposal shows up.
**Workaround**
I will sometimes type 3 characters, hit escape to dismiss the popup, and hit the hotkey. The popup then shows the proposals immediately. This workaround seems to be faster than typing 15 characters. It is also less work than typing 15 characters correctly.
**Settings**
I have the Content Assist with Java Type Proposals to popup whenever I type an alpha or : or . character. The activation delay is 1 ms.
Here are my Preferences > Java > Editor > Content Assist settings:
Auto activation delay: 1
Auto activation triggers for Java: `abcdefghijklmnopqrstuvwxyz:.ABCDEFGHIJKLMNOPQRSTUVWXYZ
**Suspicion**
I suspect that Content Assist pops up with only 1 character typed. It then gets stuck loading everything for that 1 character. Typing a single character does not reproduce this.
When things are working well, the content updates rapidly as I type. Sometimes I can hit 2-3 characters before the next content update. Yet, the current lookup operation seems to cancel and the next one starts. I am wondering if the initial content lookup operation is unable to cancel quickly.
**Motivation**
The faster the right proposal shows up; the faster I can select it and move to the next thing. When Content Assist is working well, my programming speed is very fast.
Contributor guide
Research direction
Reproduce the delay using Java Editor Content Assist with a 1 ms auto-activation delay and the listed Java triggers. Compare rapid typing with the escape-and-reopen workaround, then trace the Java Type Proposals lookup and its cancellation behavior. Done means proposals populate promptly while typing and stale lookups do not block newer content.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- developer-experience
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100