new Cache();

[jakearchibald]

To keep @domenic happy (well, and others) the cache should have a constructor.

var cache = new Cache();

It should behave similar to:

var cache = await caches.open(SECRET_TOKEN);
await caches.delete(SECRET_TOKEN);

You can add items to it, remove items from it, everything you can do with a cache, the implementation will likely be disk-backed. Once it's GC'd, it's associated items should be effectively deleted.

We can look into caches.set(name, cache) and the problems that come with it later.

[annevk]

It cannot behave similar to something that is asynchronous.

[jakearchibald]

That's why I chose "similar". I mean it should behave like a cache that never existed in caches.

My point was the implementation isn't out-of-this-world, because we already have to deal with caches that are no longer in caches and clean up on GC.

[yoshisatoyanagisawa]

Bug Triage:
There should not be actual needs to implement this.