Alastair Crabtree

No, have not had a need for it so have not put any time into it, and the PR seems to have stalled.

> Tip: > To prevent IntelliSense from suggestion both `Set` and `Add` you can add [`[EditorBrowsable(EditorBrowsableState.Never)]`](https://docs.microsoft.com/en-us/dotnet/api/system.componentmodel.editorbrowsableattribute?view=netcore-3.1) to the obsolete methods. Did not know that, very useful! Let's use it.

This can be achieved by disposing the implementation of `ICacheProvider` which is typically the `MemoryCacheProvider` and then creating a new instance of `CachingService` with a new provider instance. ```csharp //...

I have been a little hesitant about including this feature, for the same reason that it is not already implemented in MemoryCache, which is that it is both non trivial...

> Removal of all keys should not be labeled "a code smell in general". There is the perfectly valid case ... No not always I agree, but often I would...

> Given the amount of comments on the PR that say otherwise, I should think there's enough compelling reason to back down and allow the users of your framework to...

I have not seen that pattern of a version in the key before, but I like it so thanks for sharing it. A slight variation that would also work and...

What you hve done is correct but frankly the current `DefaultCachePolicy` is a bit ugly and unusual and could do with a re-write to use the new Options pattern that...

Some code seems to be missing - for example I cant see any code that generates the logs you included. Perhaps a couple of suggestions: - Check that your key...

Because of the changes to underlying APIs in MemoryCache when I moved LazyCache to version 2, some additional locking was required and because it is async in places SemaphoreSlim is...