Allow non-recursive select() with lambdas #8
Conversation
This file contains 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
…rows to indicate the relative depth from the current node's perspective at which to search, like in r => r => r.name == "ChildTag"
…h for nodes matching, or requiring the current node to already match the start condition, where a return value of null rather than false opts for the latter
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The feature works by accepting additional arrows to indicate the relative depth from the current node's perspective at which to search, like in r => r => r.name == "ChildTag".
It can help avoid ambiguous results and speed up searches tremendously.
Mixing in ternary operators allows to decide for every visited node whether or not to recurse into its children.
An example for this approach is given in nested-lambda-demo.html.