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 methane, rhettinger, serhiy.storchaka
Date 2017-04-01.15:53:26
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1491062006.6.0.951898984496.issue29961@psf.upfronthosting.co.za>
In-reply-to
Content
FWIW, I've long considered this to be a feature of set and dicts, it is the only way a user can affect sparseness.  For lookup only sets, the extra sparseness is a virtue (fewer collisions).  So, I would like to leave the current code in-place.  

With sets the goals are different from dicts.  I place less value on compactness and more value on fast membership testing.  And with dicts, the norm is that the looked-up key usually exists.  With sets, the goal isn't looking an element known to be in the set, but more about determining whether an element is in the set.  Accordingly, sets have to optimize for misses as well as hits.

In the future, please assign set feature requests to me so that I don't miss them.
History
Date User Action Args
2017-04-01 15:53:26rhettingersetrecipients: + rhettinger, methane, serhiy.storchaka
2017-04-01 15:53:26rhettingersetmessageid: <1491062006.6.0.951898984496.issue29961@psf.upfronthosting.co.za>
2017-04-01 15:53:26rhettingerlinkissue29961 messages
2017-04-01 15:53:26rhettingercreate