RetroSearch Browse

Mon Sep 19 07:26:02 CEST 2005 · https://mail.python.org/pipermail/python-dev/2005-September/056475.html

François Pinard wrote:

> The only practical reason to like this feature is sparing the need of
> finding an otherwise useless name for the formal argument.

If the argument represents a coherent enough concept
to be passed in as a tuple in the first place, it
should be possible to find a meaningful name for it.
Otherwise the elements should probably be passed in
as separate arguments.

> Yet, if I was given the choice between nested tuple function arguments,
> and faster argument processing, the latter would win instantly.

I believe that exactly the same bytecode results either
way, so there's no speed advantage or penalty.

Greg

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

Showing content from https://mail.python.org/pipermail/python-dev/2005-September/056475.html below:

[Python-Dev] removing nested tuple function parameters