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/2013-May/126500.html below:

[Python-Dev] PEP 443 - Single-dispatch generic functions

[Python-Dev] PEP 443 - Single-dispatch generic functions [Python-Dev] PEP 443 - Single-dispatch generic functionsEthan Furman ethan at stoneleaf.us
Fri May 24 02:20:23 CEST 2013
On 05/23/2013 02:02 PM, Ronan Lamy wrote:
> 2013/5/23 Łukasz Langa <lukasz at langa.pl <mailto:lukasz at langa.pl>>
>
>     On 23 maj 2013, at 20:13, Éric Araujo <merwok at netwok.org <mailto:merwok at netwok.org>> wrote:
>
>     > Question: what happens if two functions (say in two different modules)
>     > are registered for the same type?
>
>     Last one wins. Just like with assigning names in a scope, defining methods
>     in a class or overriding them in a subclass.
>
>
> This is a serious annoyance, considering that there are several places where a large library can reasonably define the
> implementations (i.e. with the class, with the function, or in some utility module). Note that in contrast with the case
> of functions in a module or methods in a class, linting tools cannot be expected to detect a duplication between
> functions with different names defined in different modules.

What would you suggest happen in this case?

--
~Ethan~
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