Async Cache is caching exceptions about async HOT 5 OPEN

It caches the actual result, which is reasonable.
Only caching successful futures is more of a "retry" behavior than a cache.

Meaning that a cache which doesn't cache errors is a reasonable thing, but a different feature than this async cache.

We could have both, or the current cache could have a flag.

from async.

Creating a new class only for this functionality can be redundant, because AsyncCache and AsyncMemoizer are showing behaviour when error occurred. We can introduce a flag. What's your opinion on this?

from async.

A flag is probably the simplest approach.
Extra work which only happens if an error occurs should not be a problem.

Still means that the default will still be the current behavior.

from async.

Sure, adding a new flag with the name canRetry. Or should we name this flag something else?

from async.

Added new variable _canCacheException it's making more sense over canRetry

from async.