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

Shouldn't lambdas be unary? #2

Open
lhorie opened this issue Nov 7, 2017 · 3 comments
Open

Shouldn't lambdas be unary? #2

lhorie opened this issue Nov 7, 2017 · 3 comments

Comments

@lhorie
Copy link

lhorie commented Nov 7, 2017

e.g. map(parseInt) does funky things due to argument distribution

@MattMcFarland
Copy link
Contributor

MattMcFarland commented Nov 8, 2017

Yep! Very true! They should be. We should look into this!

I think one of the reasons why we didn't do this previously is that we ran into an issue with forcing the unary design and keeping the functions "curryable", but only because of the current architecture . So with some refactoring this is totally possible, and I believe worth doing.

@wshager
Copy link

wshager commented Nov 12, 2017

You could write _ => parseInt(_,10) or use partial application...

@ronnross
Copy link
Member

@MattMcFarland I agree let's look into to this.

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

No branches or pull requests

4 participants