Say there's a challenge with two inputs. Can we submit a function signature like this?
a=>b=>...
Instead of
(a,b)=>...
The function then becomes callable as f(a)(b) instead of f(a,b), if we provide example usage. Is this considered acceptable, or should it be added to "standard loopholes"?
You just have to specify how to call it in your answer. It's no different than a submission that expects a certain type of input input (command line args vs. STDIN, for example).
This is just shifting work to the caller. Taking that to the nth degree, can't you just submit c=>c() to every challenge, explaining that your function needs you to call it with the argument z=>...insert actual code here...?
I don't see any reason why the conventions of function calling in Haskell should affect the conventions of function calling in Javascript.
My reasoning is that the output is wrong.
If the challenge was:
Take two integers
aandband output the sum ofaandb.
and your answer was:
a=>b=>a+b
then your answer is in the form of a function (a=>...), but the output of this function is another function instead of "the sum of a and b".
f(a)(b)?
\$\endgroup\$
\xy.xy is the same as \x.\y.xy. (If you don't: basically, chaining functions as a=>b=> is the same as (a,b)=>).
\$\endgroup\$
Commented
Feb 15, 2016 at 3:16
f(a)(b), but note that you are actually calling the outer and the inner function which seemed like processing outside of the solution to me. If your answer is the outer function, I feel like you should only be allowed to call the outer function.
\$\endgroup\$
Commented
Feb 15, 2016 at 3:20
f(a)(b) is reasonable so long as its stated that it should be called that way.
\$\endgroup\$