RetroSearch Browse

Sat Jun 18 17:59:07 CEST 2005 · https://mail.python.org/pipermail/python-dev/2005-June/054326.html

Hi,

Raymond Hettinger wrote:
> I think it unwise to allow x to be any expression.  Besides altering
> existing semantics, it leads to code redundancy and to a fragile
> construct (where the slightest alteration of any of the expressions
> triggers a silent reversion to O(n) behavior).

What would happen if 'x' were to be an object whose class has a __eq__
that is defined in an odd way, e.g. having side effects?
Might this mean behaviour change even if 'x' is a local variable?

yours,
Gerrit Holl.

-- 
Weather in Twenthe, Netherlands 18/06 17:25:
	24.0°C   wind 3.1 m/s NE (57 m above NAP)
-- 
In the councils of government, we must guard against the acquisition of
unwarranted influence, whether sought or unsought, by the
military-industrial complex. The potential for the disastrous rise of
misplaced power exists and will persist.
    -Dwight David Eisenhower, January 17, 1961

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

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

[Python-Dev] Multiple expression eval in compound if statement?