Support managed cached values about zio-cache HOT 6 CLOSED

@ithinkicancode The lookup function would return a ZManaged instead of a ZIO and then when the lookup function is run we would evaluate the acquire action of the ZManaged and store the release action in the cache, running it when the cache entry was evicted. The entire cache would likely be created in the context of a managed effect to ensure that all acquired resources were released when that scope was closed.

from zio-cache.

Released in https://github.com/zio/zio-cache/releases/tag/v0.1.2. I think we can close this issue now!

from zio-cache.

Hi @vigoo, can you elaborate or can you give an example? Currently, a cache value is stored as exit: Exit[Error, Value] in the MapValue.Complete case class. Do you mean it should be replaced as exit: ZManaged[Any, Error, Value]?

from zio-cache.

I start working on that issue but would appreciate some advice if possible (see #71 )

from zio-cache.

The interface of the cache itself must change, since the resource management mechanism must be aware of when a resource is done being used. This implies: not only is the lookup function resourceful, but also the get function on the cache is resourceful.

@adamgfraser It will be interesting to see how this shakes out in a 2.0 world.

from zio-cache.

I think I got something working on #71 and I would appreciate some feedback on the question I added as comments in my code before going forward with this PR.
Also the trackAccess function is really obscure to me, I really don't understand how it works and I am not sure to understand its goal (make sure that cache does not exceed is capacity I guess)?

from zio-cache.