This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author serhiy.storchaka
Recipients Jim.Jewett, Jimbofbx, Ramchandra Apte, jcea, pitrou, rhettinger, serhiy.storchaka, skrah
Date 2012-04-07.12:28:59
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1333801879.21808.9.camel@raxxla>
In-reply-to <1333793995.9.0.0277489989882.issue14478@psf.upfronthosting.co.za>
Content
> > I recommend that __hash__ should use functools.lru_cache for caching.
> Why would you do such a thing? A hash value is a single 64-bit slot, no need to add the memory consumption of a whole dictionary and the runtime cost of a LRU eviction policy when you can simply cache the hash in the object itself (like we already do for strings)...

It was a joke (I think). Taking into account the fact that LRU cache
uses a hashtable and need to calculate the hash of arguments (i.e., the
Decimal self) to get the cached value of hash.
History
Date User Action Args
2012-04-07 12:28:59serhiy.storchakasetrecipients: + serhiy.storchaka, rhettinger, jcea, pitrou, skrah, Jimbofbx, Ramchandra Apte, Jim.Jewett
2012-04-07 12:28:59serhiy.storchakalinkissue14478 messages
2012-04-07 12:28:59serhiy.storchakacreate