HashIndex values not dropped until the end of the program?

[Dreaming-Codes]

What's happening here?

[Dreaming-Codes]

Temporary switched to HashMap since my app rely on the value getting dropped

[wvwwvwwv]

I guess HashIndex is not for you if you need to depend on an exact timing of ‘drop’ calls.

[wvwwvwwv]

Hi! Values in a HashIndex are not immediately dropped, and they may last longer than the HashIndex instance.

1. When an entry is removed, they are just marked deleted, because there might be lock-free readers of it. The instance is passed to the EBR garbage collector when the bucket is rearranged (frequent remove & insert triggers a rearrange), the HashIndex is resized, or the HashIndex is dropped.
2. The EBR garbage collector may not drop garbage instances until the end of the process.

[Dreaming-Codes]

1. When an entry is removed, they are just marked deleted, because there might be lock-free readers of it. The instance is passed to the EBR garbage collector when the bucket is rearranged (frequent remove & insert triggers a rearrange), the HashIndex is resized, or the HashIndex is dropped.

Is there a way to listen for deletion?

[wvwwvwwv]

No, and it's not just about knowing when the entry is dropped, but the fact that the entry can survive indefinitely. That's a cost for allowing lock-free read.

[wvwwvwwv]

If you have any other questions, don't hesitate to open a new discussion thread!