I am not sure yet about how to deal with this one.

I agree that there is space to reuse some code for hash tables in shared memory, but I feel that we should have dedicated code for it, not to mix it with the one in pkg memory. It will avoid all these if checks to lock/unlock, as we use hash tables to speed up search, it feels we need to keep it optimised.

Moreover, iirc and hope not to confuse with other api, some of the macros are even now used for hash tables in memory, just that the lock/unlock of the slot is done in the implementation code, not in the core code.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.