Path: csiph.com!usenet.pasdenom.info!aioe.org!news.stack.nl!newsfeed.xs4all.nl!newsfeed1.news.xs4all.nl!xs4all!newsgate.cistron.nl!newsgate.news.xs4all.nl!post.news.xs4all.nl!not-for-mail
MIME-Version: 1.0
In-Reply-To: <53BC38A0.7030100@jmunch.dk>
References: <53BC05FB.4050707@jmunch.dk> <CAPTjJmoD5gfwpcW_45bzO846gFYMGH6+9TYowSea0SPpe-o__A@mail.gmail.com> <53BC38A0.7030100@jmunch.dk>
Date: Wed, 9 Jul 2014 04:42:18 +1000
Subject: Re: NaN comparisons - Call For Anecdotes
From: Chris Angelico <rosuav@gmail.com>
Cc: "python-list@python.org" <python-list@python.org>
Content-Type: text/plain; charset=UTF-8
Precedence: list
Newsgroups: comp.lang.python
Message-ID: <mailman.11651.1404844945.18130.python-list@python.org>
Lines: 60
NNTP-Posting-Host: 2001:888:2000:d::a6
Xref: csiph.com comp.lang.python:74199

On Wed, Jul 9, 2014 at 4:29 AM, Anders J. Munch <2014@jmunch.dk> wrote:
> Chris Angelico wrote:
>> For hash keys, float object identity will successfully look them up:
>
>
> Except you can't expect to rely on object identity in most interesting
> cases.
>
>>>> x = float('nan')
>>>> import struct
>>>> y = struct.unpack('<f', struct.pack('<f', x))[0]
>>>> d[x] = "found"
>>>> d[y]
>
> Traceback (most recent call last):
> File "<stdin>", line 1, in <module>
> KeyError: nan
>
> and also:
>
>>>> def f(): return float('inf')/float('inf')
>>>> f() == f()
> False
>>>> f() is f()
> False

Neither of those examples is anything to do with object identity. In
the first case, you pack the value and recreate an equivalent of the
same type with the same value. In the second, you independently
construct two floats with the same value. Both times, you have
equivalence (both are NaN), but not identical objects.

> Let me conjure up a simple example:
>
> | class Monitor(Thread):
> | def run(self):
> | old = self.get_current_value()
> | while not self.Terminated:
> | new = self.get_current_value()
> | if new != old:
> | print(time.asctime(), "changed to", new)
> | old = new
> | time.sleep(1)
>
> This is a completely generic change detection algorithm, and not a
> "floating-point algorithm" in any way: It will work on strings, lists, sets,
> anything that get_current_value returns, including non-NaN floats. You don't
> need to know anything about floating-point representation to write or use
> such an algorithm, why should you? It works on tuples, sets, lists, serial
> port handles, module objects, pretty much anything you can imagine -- except
> NaN floats.

You also have to cope with objects that define __eq__ or __ne__. If
you know that you have a monitor like that, then you make sure that
the value is something comparable; there are plenty of reasons to have
to be careful there. (Consider, for instance, what happens if
get_current_value() returns a list. Mutating that list can change
whether or not it's equal to something else.)

ChrisA