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 methane
Recipients methane, rhettinger, serhiy.storchaka, xiang.zhang
Date 2016-09-19.04:01:38
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1474257699.6.0.930133279223.issue28199@psf.upfronthosting.co.za>
In-reply-to
Content
Current compact ordered dict implementation is bit different from yours.
When there was removed item, there are NULL entries in ma_entries, instead of swapping last item and deleted item.
It's important to keep insertion order.

But it's easy to detect clean dict. Your suggestion can be used when:

* dk_lookup == lookdict_unicode_nodummy: There are no dummies, all keys are unicode, and no NULL entries.
* ma_used == dk_nentries: It means there are no NULL entries. (All deletion except .popitem() is allowed)

I think dictresize for split table can be split function. But I don't know it can improve performance or readability.
History
Date User Action Args
2016-09-19 04:01:39methanesetrecipients: + methane, rhettinger, serhiy.storchaka, xiang.zhang
2016-09-19 04:01:39methanesetmessageid: <1474257699.6.0.930133279223.issue28199@psf.upfronthosting.co.za>
2016-09-19 04:01:39methanelinkissue28199 messages
2016-09-19 04:01:38methanecreate