allegro / allegro/bigcache

Why doesn't bigcache consider designing expiration time for each cache key?

Open
#360 4 comments 2 reactions 0 assignees View on GitHub
question
Dominant language
Go
Stars
8.2k
Forks
614
Avg merge
5d 12h
Merged PRs (30d)
1

Description

During the process of using and reading the source code, it was found that in each instance of bigcache, all key-value pairs can only be set with a unified expiration time. A `time.Ticker` is used to periodically check if the cache has expired based on the interval set by `CleanWindow`. So why wasn't a method considered to allow setting expiration time for each cache key?

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.