3 ms·
> So on `get` if we're in the process of resizing Not just get, but set also, right? Otherwise I would think a large group of set operations that overflowed m
by kbenson 6y ago
> So on `get` if we're in the process of resizing
Not just get, but set also, right? Otherwise I would think a large group of set operations that overflowed more than once might be problematic to deal with. Or maybe I'm missing something that makes that a non issue?
- tkhattra 6y agoyes, set also. go's map implementation uses this technique - allocate a new array of buckets and gradually migrate from old to new buckets (i think it does the migration during set and delete only, not get).
- deleted 6y ago[deleted]