Talk:Partial function application: Difference between revisions
Content added Content deleted
(ββIs Scala correct?: Yes, you can pass arity 3 function to map.) |
(added suggestions) |
||
Line 350: | Line 350: | ||
# The ''compilation technique'' that allows function thunks or closures to be "partially applied" instead of only unapplied or fully applied. |
# The ''compilation technique'' that allows function thunks or closures to be "partially applied" instead of only unapplied or fully applied. |
||
The task here should probably be about the first, perhaps also the second. —''[[User:Ruud Koot|Ruud]]'' 15:35, 21 April 2011 (UTC) |
The task here should probably be about the first, perhaps also the second. —''[[User:Ruud Koot|Ruud]]'' 15:35, 21 April 2011 (UTC) |
||
== Suggested changes to the task description == |
|||
1) There is no need to require functions to be named <code>f1</code>, <code>f2</code>, <code>fsf1</code> or <code>fsf2</code>, and doing so excludes solutions in languages that don't allow digits to be used in identifiers. |
|||
2) The wording "partially apply <code>f1</code> to <code>fs</code>" should be changed to "partially apply <code>fs</code> to <code>f1</code>" because it's more conventional to speak of functions being applied to arguments than vice versa, and in this case <code>f1</code> is the argument. |
|||
3) Please be consistent about distinguishing between functions themselves and expressions in which they are applied to an argument. The wording "create a function <code>fs(f,s)</code> that takes a function <code>f(n)</code> ..." should be changed to "create a function <code>fs</code> that takes a function <code>f</code> ...". The expression <math>f(n)</math> refers conventionally not to the whole function <math>f</math> but to the single output associated with the argument <math>n</math> (unless you're an economist). |
|||
--[[User:Sluggo|Sluggo]] 18:09, 14 June 2011 (UTC) |