Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #91522 > unrolled thread
| Started by | Serhiy Storchaka <storchaka@gmail.com> |
|---|---|
| First post | 2015-05-30 12:32 +0300 |
| Last post | 2015-05-30 12:32 +0300 |
| 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: Minus operator versus unary minus Serhiy Storchaka <storchaka@gmail.com> - 2015-05-30 12:32 +0300
| From | Serhiy Storchaka <storchaka@gmail.com> |
|---|---|
| Date | 2015-05-30 12:32 +0300 |
| Subject | Re: Minus operator versus unary minus |
| Message-ID | <mailman.219.1432978385.5151.python-list@python.org> |
On 30.05.15 12:09, Peter Otten wrote: > Serhiy Storchaka wrote: >> On 30.05.15 10:56, Peter Otten wrote: >>> The following modification of the collections.Counter implementation >>> >>> https://hg.python.org/cpython/rev/fe4efc0032b5 >>> >>> was just checked in with the line >>> >>> result[elem] = 0 - count >>> >>> Does this have an advantage over the obvious >>> >>> result[elem] = -count >>> >>> ? >> >>>>> x = 0.0 >>>>> -x >> -0.0 >> >> >>>>> 0 - x >> 0.0 > > That's a subtle difference, but does it matter in the context of the patch? I don't know. Perhaps there is more meaningful difference for decimals. This code is not new (see https://hg.python.org/cpython/rev/e908ebc160f0).
Back to top | Article view | comp.lang.python
csiph-web