You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Feature request: Add support for lambda and reference expressions in debug evaluation #281
Stream.of(strings).forEach(s -> System.out.println(s))
Lambda expressions cannot be used in an evaluation expression
Stream.of(strings).forEach(System.out::println)
Reference expressions cannot be used in an evaluation expression
Reacted by Krzysztof Kaczmarczyk, Tim, Nicholas Guetter, Leonardo Ramos Duarte, Felipe Tuyama and Alexander Gabriel Castañeda Estévez
Gayan Perera (@gayanper) we're a small team, currently we have limited resource for this. Appreciate a lot if the community can contribute this feature in the upstream JDT.
Activity
andxu commentedon Apr 23, 2018
Eclipse doesn't support it and we are leverage their jdt libraries for expression evaluation, so it will be a big change to have a own implemented expression evaluation, see https://stackoverflow.com/questions/42346169/java-eclipse-lambda-expressions-cannot-be-used-in-an-evaluation-expression?utm_medium=organic&utm_source=google_rich_qa&utm_campaign=google_rich_qa
bkbonner commentedon Feb 6, 2019
Is this still true? I followed the path. It sort of critical to be able to debug lambdas.
It looks like the bug in eclipse is here: https://bugs.eclipse.org/bugs/show_bug.cgi?id=448473 (the other bug in the stack overflow was marked as a duplicate of this)
gayanper commentedon Jul 27, 2019
Andy Xu(devdiv) (@andxu) Didn't you though of contributing a fix for JDT on this ?
testforstephen commentedon Jul 29, 2019
Gayan Perera (@gayanper) we're a small team, currently we have limited resource for this. Appreciate a lot if the community can contribute this feature in the upstream JDT.
testforstephen commentedon Jul 15, 2020
The upstream has added the lambda support for evaluation, and already integrated to the latest VS Code Java Debugger. Will close the issue.