Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Refactor kleisli/function order to make code flow better #11

Open
neutropolis opened this issue Mar 19, 2024 · 1 comment
Open

Refactor kleisli/function order to make code flow better #11

neutropolis opened this issue Mar 19, 2024 · 1 comment
Labels
enhancement New feature or request

Comments

@neutropolis
Copy link
Member

At the time being, we supply functions at the very first parameter. I thought this was nicer since syntax order is closer to Haskell, but since we don't have do-notation or for-comprehensions I think that we can benefit from having the kleisli defined as the second parameter, as in:

bind[foo] {[a]
  bind[bar] {[b]
    bind[baz] ret
  }
}
@neutropolis neutropolis added the enhancement New feature or request label Mar 19, 2024
@neutropolis
Copy link
Member Author

Let's wait for the motivation and examples to determine if this is a good or bad idea...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant