I'm trying out the new experimental CacheStore and am wondering if it supports caching negative results? We are trying to use it against sparse arrays written with write_empty_chunks: False. From a cursory look at the CacheStore implementation it seems that a negative (None) result might remove a cache entry instead of caching an empty/negative result.

When using fixed sparse zarr arrays caching negative entries would be very helpful. There are dynamic use cases where arrays might still change where you'd like to have different behaviors but the default should not have worst performance is sparse regions.