Is there a reason that dict.copy() runs like an update()? It creates a new dict object, then re-hashes and inserts every element one-by-one, complete with collisions. I would have expected a single pass to update refcounts, an allocation for identical size, and a memcpy to polish it off. Raymond
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4