[Feature Request] onevict, callback feature

[ouvaa]

possible to have an onevict call back feature for both the ttl and non ttl version?

[phuslu]

I've been thinking about this idea for a long time, but I haven't done it yet.

1. phuslu/lru does not have an real(active) evict policy. If a WithEvict Option is provided, users may misunderstand/complain about why the item not being evicted when the TTL expires.
2. Considering the above, I need a good Option name to avoid misuse/misunderstanding. I don’t have a good idea yet. Maybe WithListener is a potential candidate.

[phuslu]

maybe I need to implement a simple/cheap evict policy in future, e.g. a random scan policy which similar with redis.

[ouvaa]

@phuslu chatgpt can help suggest some good names.

[izturn]

any progress?

[esp32wrangler]

It is easy to implement some scanner feature in/around a wrapper if some user really needs it, but to allow that, there has to be at least a callback when an item is evicted before expiration. So please add at least that callback, or give us some pointers on how it would be easiest to implement it.