"external memory management" can't be addressed more generally with move constructors of table elements and emplace rather than insert?
On Mon, Aug 13, 2018 at 2:23 PM, Walt Karas <wka...@oath.com> wrote: > A layered approach to multiple indexes is to have all or all but one > table contain pointers to the contained objects. > > On Mon, Aug 13, 2018 at 2:19 PM, Walt Karas <wka...@oath.com> wrote: >> I was fooling with one writer / multi reader some for any data >> structure. Another twist to it is to have two copies of the data >> structure. You have to make updates twice, the advantage being there >> is always a coherent version of the data structure available for >> reading. >> >> http://coliru.stacked-crooked.com/a/1074bd17521d6587 >> >> >> On Mon, Aug 13, 2018 at 1:28 PM, Alan M. Carroll >> <a...@network-geographics.com> wrote: >>> I've written up some of my notes and thoughts on hash containers and how to >>> proceed here - https://solidwallofcode.github.io/notes/hash-table.en.html >>> >>> Please respond to this email string if you have comments of your own. >>>
