A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2004-February/042694.html below:

[Python-Dev] Re: PEP 309, function currying

[Python-Dev] Re: PEP 309, function curryingMoore, Paul Paul.Moore at atosorigin.com
Tue Feb 24 05:05:21 EST 2004
From: Peter Harris
> Yes, that's currying alright, which PEP 309 does in no way describe.
> Hmm.
> OK, there is way too much imprecise thinking behind that PEP. Sorry.

> Quick unscientific name poll.  Who likes...

> * curry()
>
> * closure()
>
> * partial()
>
> * partial_apply()
>
> * delayed()
>
> * other ?

I like curry(). The others don't bring the right concept to mind for me.
I apologise if this offends the purists, but *all* of the recent attempts
to "clarify" the difference between partial application and currying have
simply confused me.

If curry() gets screams of outrage, someone suggested bind() to follow the
Boost C++ library's usage. That's tolerable, although I find it too generic
a word.

Paul

More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4