pico-lambda
pico-lambda copied to clipboard
Shouldn't lambdas be unary?
e.g. map(parseInt) does funky things due to argument distribution
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.
You could write _ => parseInt(_,10) or use partial application...
@MattMcFarland I agree let's look into to this.