This repository was archived by the owner on Jul 8, 2022. It is now read-only.
Initial implementation of Scala-style implicit functions. #4
Conversation
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
|
It's not yet clear to me from the enforestation document (probably just because I don't know the implementation well enough) where I would put similar code to handle |
|
This now handles |
Following the style of the `fancy-app` package. Does not handle operators yet, nor does it handle `.`. This makes `f(_,1)` expand to `fun(x): f(x,1)`. Main design question is the behavior of multiple _ in the application. This PR causes each _ to become a distinct function argument, in order of their appearance. Alternative designs: - multiple _ all become the same binding - multiple _ are illegal
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Following the style of the
fancy-apppackage. Does not handleoperators yet, nor does it handle
..This makes
f(_,1)expand tofun(x): f(x,1).Main design question is the behavior of multiple _ in the application.
This PR causes each _ to become a distinct function argument, in
order of their appearance. Alternative designs: