Message157732
| Author |
pitrou |
| Recipients |
Jim.Jewett, Jimbofbx, Ramchandra Apte, jcea, pitrou, rhettinger, serhiy.storchaka, skrah |
| Date |
2012年04月07日.12:35:14 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1333801792.3814.0.camel@localhost.localdomain> |
| In-reply-to |
<1333801879.21808.9.camel@raxxla> |
| 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.
Damn. Shame on me for not understanding Raymond's humour :-) |
|