You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
that values does not contain any nulls if I had not inserted any into cache,
that cache does not delete elements while timers do not have a chance to run and
that a function named get does not delete elements.
Currently memory-cache deletes elements both with timers and as a side-effect within get among other methods. I think it would be helpful to write such design decisions high up in the README. The API description of get in the README does not explain this behavior. The uncertainty in the result of del is the only hint about side-effects.
The text was updated successfully, but these errors were encountered:
I'd like to do something like this:
Based on the documentation, I expect:
values
does not contain anynull
s if I had not inserted any intocache
,cache
does not delete elements while timers do not have a chance to run andget
does not delete elements.Currently memory-cache deletes elements both with timers and as a side-effect within
get
among other methods. I think it would be helpful to write such design decisions high up in the README. The API description ofget
in the README does not explain this behavior. The uncertainty in the result ofdel
is the only hint about side-effects.The text was updated successfully, but these errors were encountered: