Anonymous user
Talk:Partial function application: Difference between revisions
→Explicit curry vs Partial application: Anyone else up for it?
(ok, so) |
(→Explicit curry vs Partial application: Anyone else up for it?) |
||
Line 46:
:::::Touché. If not mentioning the other args was made a task restriction, I'm pretty sure it could not be done in Go. Go requires static typing yet has no way of specifying one function type in terms of another function type. It might be a good restriction. Simple closures are already demonstrated in tasks like Function composition and First class functions. I might reword it "Note that in the partial application of a parameter, (in the above case param1), the only inputs are f and param1. The return value and arguments of f' are determined solely by f and are not explicitly mentioned. This is an essential feature of partial function application." I might also remove "( s )" from task bullets 4 and 5, so that they read just "Partially apply f1 to fs to form function fsf1." It's a little more cryptic, but it removes a possible suggestion that it's okay to specify the argument list of fsf1. —[[User:Sonia|Sonia]] 18:32, 13 April 2011 (UTC)
:::: Thanks Sonia. Anyone else OK with such an update? (Remember, the idea isn't to exclude Go; it is to more explicitely define partial application). --[[User:Paddy3118|Paddy3118]] 21:08, 13 April 2011 (UTC)
| |||