Community
Participate
Working Groups
Function<int[], int[]> m1 = int[]::clone; The method binding for #clone in TypeMethodReference in the above example is a synthetic method binding (with private static modifiers) which is not helpful to the clients. The method binding for #clone resolves to Object#clone() in MethodInvocation in the following example: int[] ints = new int[] {1, 2, 3}; ints.clone(); Also see bug 333665, which says that the binding should be targeted to the Array implementation of clone(). For now, the bindings for MethodReferences to clone() of an array type should also resolve to Object#clone(), like in MethodInvocations. Once bug 333665 is fixed, bindings for MethodReferences and MethodInvocations should point to the array type's variant of clone().
(In reply to Noopur Gupta from comment #0) > a synthetic method binding (with private static modifiers) Same problem as bug 429813: The DOM bindings should not contain the generated helper method but the actually referenced method.
No progress on this. Moving out to 4.6.
No progress yet and unlikely to get time during 4.6. Moving out.
Bulk move out of 4.8
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.
