RFC - Expiry based on passed in function (option during cache creation) about ttlcache HOT 2 CLOSED

How/when would this function be called?

The capacity and TTL checks are rather efficient, i.e., they aren't performed randomly and additional internal queues are being used for that too. As I see it, the only way this dynamic function could work is if the user provided some duration after which it would be called (or DeleteExpired() would be called by the user). But even then the cache would have to iterate over all the items as no internal queues could be used.

I don't see how this addition could benefit this library, however, I understand that sometimes items need to be dynamically deleted. I think the best way to achieve this would be by having a method that would allow the user to iterate over the items in the cache. We have an issue for that as well: #71

from ttlcache.

for some reason, the eviction was being done through a timer/scheduled function..which means my idea would have had legs. looking back, it seems to clean itself on accesses.

I think it will be best to have an external cleaning component that accepts the cache as an input and iterate on schedule to clean it.

from ttlcache.