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 rhettinger
Recipients Rhamphoryncus, chemacortes, jcea, mark.dickinson, pitrou, rhettinger
Date 2009-02-11.22:04:16
SpamBayes Score 5.9837466e-06
Marked as misclassified No
Message-id <1234389858.14.0.0634193022618.issue5186@psf.upfronthosting.co.za>
In-reply-to
Content
At four bits, you may be throwing away information and I don't think
that's cool.  Even if some selected timings are better with more bits
shifted, all you're really showing is that there is more randomness in
the upper bits than the lower ones.  But that doesn't mean than the
lower one contribute nothing at all.

I'm *much* more comfortable with a byte-swap, rotation, or xoring-in
upper bits than with shifts that potentially destroy entropy. 
Otherwise, your taxing apps that build giant sets/dicts and need all
distinguishing bits to avoid collision pile-ups.
History
Date User Action Args
2009-02-11 22:04:18rhettingersetrecipients: + rhettinger, jcea, chemacortes, mark.dickinson, Rhamphoryncus, pitrou
2009-02-11 22:04:18rhettingersetmessageid: <1234389858.14.0.0634193022618.issue5186@psf.upfronthosting.co.za>
2009-02-11 22:04:16rhettingerlinkissue5186 messages
2009-02-11 22:04:16rhettingercreate