Breakpoints for lambdas.#571
Open
lahodaj wants to merge 1 commit into
Open
Conversation
oracle-contributor-agreement
Bot
added
the
OCA Verified
lahodaj
force-pushed
the
lambda-breakpoints
branch
from
80e6640 to
d14de66
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This is a draft/prototype incorporating apache/netbeans#9285 into the extension, for testing purposes. It adds an ability to put breakpoints in individual lambdas. Internally, the lambdas are identified by the sequence number on their (starting) line. Please look at the NB PR for some details.
In VS Code, it may look like:
Please see also #64.