Bugzilla – Full Text Bug Listing
| Summary: | "Use lambda where possible" cleanup fails when functional interface initialized before referenced member | ||
|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | Hollis Waite <hwaite> |
| Component: | Core | Assignee: | JDT-Core-Inbox <jdt-core-inbox> |
| Status: | CLOSED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | ||
| Version: | 4.6 | ||
| 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. If you have further information on the current state of the bug, please add it. 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. |
"Use lambda where possible" cleanup converts public class Test { private final Object mObj; private Consumer mConsumer = new Consumer() { public void accept(Object pParam) {mObj.toString();} }; Test() {mObj = "";} } to public class Test { private final Object mObj; private Consumer mConsumer = pParam -> mObj.toString(); Test() {mObj = "";} } Output code fails with error "The blank final field mObj may not have been initialized".