Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #74263 > unrolled thread
| Started by | Ethan Furman <ethan@stoneleaf.us> |
|---|---|
| First post | 2014-07-09 09:42 -0700 |
| Last post | 2014-07-09 09:42 -0700 |
| Articles | 1 — 1 participant |
Back to article view | Back to comp.lang.python
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: NaN comparisons - Call For Anecdotes Ethan Furman <ethan@stoneleaf.us> - 2014-07-09 09:42 -0700
| From | Ethan Furman <ethan@stoneleaf.us> |
|---|---|
| Date | 2014-07-09 09:42 -0700 |
| Subject | Re: NaN comparisons - Call For Anecdotes |
| Message-ID | <mailman.11698.1404924234.18130.python-list@python.org> |
On 07/08/2014 07:53 AM, Anders J. Munch wrote: > > So I make this claim: float.__eq__ implementing IEEE-754 NaN > comparison rules creates real problems for developers. And it has > never, ever, helped anyone do anything. > > "Never" is a strong claim, and easily disproven if false: Simply > provide a counterexample. So that is my challenge: If you have a > program (a pre-existing and useful one, not something artificial > created for this challenge) that benefits from NaN!=NaN and that would > fail if x==x for all float objects x, then please come forward and > show it, and I'll buy you a beer the next time I'm at PyCon. I would suggest you ask for this on the numerical mailing lists instead of here -- and you may not want to offer a beer to everyone that has an anecdote for NaN behavior being useful. -- ~Ethan~
Back to top | Article view | comp.lang.python
csiph-web