We should remove IMemoryCache.Remove

[sebastienros]

To remove entries the supported scenario is to add a token (like a CancellationTokenSource) in he options of the entry.

[sebastienros]

@lodejard Will confirm if necessary.

[Tratcher]

No, that would require too much dev bookkeeping to track all of the CTSs. There's nothing wrong with removing an entry by name.

[lodejard]

There are very few places where a remove needs to occur, so there is very little additional CTS. In the few places where it does need to occur, what the code is trying to do is remove what it has added. By removing via key it can also easily remove what is being readded at the same time. That's why the operation should be expire-what-i-added-before rather than remove-by-key.

[Tratcher]

And IDistributedCache?

[lodejard]

Distributed cache and memory cache are different

[Tratcher]

@DamianEdwards

[Eilon]

Though I think there is merit to this proposal, it would make IMemoryCache too difficult to use in the most common cases people are familiar with.

[Eilon]

(Plus, a massive API change.)