An example about partial application of closures - #3
Open
Kakadu wants to merge 1 commit into
Open
Conversation
Signed-off-by: Kakadu <Kakadu@pm.me>
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
1 participant
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.
Dear @Gbury
Many thanks for your explanation. But in the current state of documentation I don't entirely understand how closures are represented, that have been already partially applied. In general I want to understand is it possible (or when) to recover from partially applied closure which parent function has been partially applied.
I added an example about partial applications in this PR
P.S. On attached SVG at the moment I don't entirely follow how a pointer to parent function does fit in memory representation described in your documentation