On Sunday, 8 June 2014 02:27:42 UTC+1, Gregory Ewing  wrote:
> Also it doesn't sit well with Python's "one obvious
> way to do it" guideline, because it means there are
> *two* equally obvious ways to call a function.

This provides a way to do something new (add class-optimized implementations 
for existing general-purpose functions). It also adds significant readability 
improvements by putting function-call chains in order.

Reply via email to