on-get callback about cacheout HOT 6 CLOSED

I'm also not sure on the utility of it, but the callback could also include whether the key there or not. That might make it a little more useful.

from cacheout.

I'm also not sure on the utility of it, but the callback could also include whether the key there or not. That might make it a little more useful.

If the key is missed, whichever is better is to set the value to None or UNSET?

from cacheout.

If the key is missed, whichever is better is to set the value to None or UNSET?

Another question around this would be whether having value always be the returned value (i.e. the existing value or the default value) and send another variable to indicate whether the key exists would be preferable over having the value only ever be the existing one. Potentially the default value could come from a default function so would having that value potentially be useful? Seems like we'd have more information with the first option.

from cacheout.

If the key is missed, whichever is better is to set the value to None or UNSET?

Another question around this would be whether having value always be the returned value (i.e. the existing value or the default value) and send another variable to indicate whether the key exists would be preferable over having the value only ever be the existing one. Potentially the default value could come from a default function so would having that value potentially be useful? Seems like we'd have more information with the first option.

Callable[[key: Hashable, value: Any, existed: bool],  None]

Add existed to indicate whether the key has existed. If existed is true, value is the real value. Otherwise, value is the default value.

from cacheout.

Callable[[key: Hashable, value: Any, existed: bool], None]
Add existed to indicate whether the key has existed. If existed is true, value is the real value. Otherwise, value is the default value.

👍

from cacheout.

Done in #38

from cacheout.