Open
Conversation
Owner
|
wow, this is amazing @lmcgrath \o/ Will merge soon(ish), thanks! |
Author
|
Woohoo! |
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
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.
Hey @qmx! I've added a simple DSL block for generating lambdas more easily, mostly because I find the multiple invokedynamic arguments required for lambdas is tough to get my head around.
In a nutshell, lambdas require the following:
Using this information, the relevant invokedynamic instruction is created to delegate into the implementation method.
Caveats:
The lambda block test (JiteClassTest#testLambda) is only run on Java 8. The test method exits if not running Java 8. I've taken steps to ensure Java 8 isn't required when using jitescript by coding all JDK 8 class names as strings. Is there a better way to manage the test given the JDK version constraint? :S
Examples: