existsObject not optimal
Open
- Dominant language
- Swift
- Stars
- 3.1k
- Forks
- 355
- PR merge metrics
- No merged PRs in 30d
Description
hi
I discovered that existsObject is doing a lot (too much) to return just a Bool. It checks the entry, decodes the object, etc... So if I use the cache to store large images, it would decode an image just to confirm that it exists in the cache
Isn't there a less expensive way to check for the presence of an object in the cache ?
Matthieu
Contributor guide
Assessment
This issue has not been assessed yet.