[Coil 3] Introduce DiskCache scoped operation? about coil HOT 2 CLOSED

Hmm generally I prefer avoiding adding functions like these to Coil for a couple reasons:

• It creates two ways to do something. Should I prefer using DiskCache.edit or DiskCache.openEditor? Providing one way to do something makes it more intuitive and clear.
• If users prefer the edit/read syntax users can add these functions themselves. If a user prefers openSnapshot/openEditor then the extension functions just increase Coil's size.
• We have to make opinionated choices. Should openEditor throw if it's null? Generally I try to avoid throwing as much as possible, but this behaviour might be preferable to some users. By requiring users to handle openEditor's null result, we force them to make their own decision.

from coil.

Gotcha

from coil.