Bugzilla – Full Text Bug Listing
| Summary: | Code completion breaks following a lambda which contains a do-while loop | ||
|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | Matthew DOnofrio <artist> |
| Component: | Core | Assignee: | JDT-Core-Inbox <jdt-core-inbox> |
| Status: | CLOSED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | gautier.desaintmartinlacaze, stephan.herrmann |
| Version: | 4.5.2 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows 10 | ||
| Whiteboard: | stalebug | ||
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're closing this bug. If you have further information on the current state of the bug, please add it and reopen this bug. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie. Note: I'd love to fix this, but no-one in the team seems to have an idea how to truly reconcile the completion parser with more and more workarounds and kludges for an increasingly opportunistic Java grammar. See e.g., bug 530556 |
Attempting to perform code completion provides "No Default Proposals". Example: import java.util.concurrent.CompletableFuture; public class Test { public static void main( String[] args) { CompletableFuture<Boolean> f = CompletableFuture.supplyAsync(() -> { do { } while (false); return true; }); f. // Cannot code complete here } }