Bugzilla – Full Text Bug Listing
| Summary: | [1.8][model] Lambda elements missing in ancestry for nested types. | ||
|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | Srikanth Sankaran <srikanth_sankaran> |
| Component: | Core | Assignee: | Jay Arthanareeswaran <jarthana> |
| Status: | CLOSED WONTFIX | QA Contact: | |
| Severity: | minor | ||
| Priority: | P3 | CC: | manoj.palat |
| Version: | 4.4 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows 7 | ||
| 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. |
interface MyFunction<T, R> { R apply(T t); default <V> MyFunction<V, R> compose(MyFunction<? super V, ? extends T> before) { return (V v) -> { class X { int field; void foo(int x) { int y = 0; System.out.println(field); } } return apply(before.apply(v)); }; // return (v) -> apply(before.apply(v)); // OK } } Hovering on field (and other variables inside class X) demonstrates that lambda elements are missing in ancestry. This is low priority - Only very uncommonly, do we expect lambdas to have nested types.