Here is my sample java code:
public class Test {
public static void main(String[] args) {
methodDepth0(
()->
methodDe
As the second picture clearly shows, Eclipse is able to trace the call hierarchy through the method call myIf.call()
inside methodDepth0
. This is correct, because the (outer) lambda implements method MyIF.call()
.
The fact that the same pattern does not work in the next nesting level looks like a bug. Please consider filing a bug for JDT/UI. TIA.
Just note, that for lambdas implementing library types like Consumer
, the number of callers into accept(T)
in a workspace may easily become unmanageable, similar to any call hierarchy through, e.g, Runnable.run()
- but that doesn't question the general usefulness of call hierarchies through lambdas.