feat: sharded peek, builder new(), ext alias parity, concurrent cache_try_get_or_set_with, retain on map stores - #294
Merged
Conversation
…et*`, wrap order-method values in `CacheValue` Breaking changes ahead of 3.0.0 final: - remove `CacheSetError`: a TTL that would overflow `Instant` bounds now stores the entry with no expiry (never expires) on every set path, matching the sharded TTL stores (`cache_set` already behaved this way). `TtlCache` / `LruTtlCache` / `TtlSortedCache` set `Cached::Error = Infallible`, so every built-in in-memory store is infallible; the `type Error` machinery remains for custom and IO stores. - rename `TtlSortedCache::insert` / `insert_ttl` / `insert_evict` / `insert_ttl_evict` to `set` / `set_with_ttl` / `set_evict` / `set_with_ttl_evict`, returning `Option<V>` instead of `Result`. - unify the LRU-family order methods on one shape: `iter_order() -> Vec<(K, CacheValue<V, M>)>` and `value_order() -> Vec<CacheValue<V, M>>` on `LruCache`, `LruTtlCache`, and `ExpiringLruCache`. `CacheValue<V, M = ()>` (new root re-export) derefs to `V`, compares against bare values, and exposes per-entry metadata via typed accessors: `expires_at()` on `LruTtlCache` entries (`M = Option<Instant>`). `LruTtlCache` no longer leaks bare `(Option<Instant>, V)` tuples. Migration guide sections 18/22/33/43 updated and 74/75 added; design doc 0020 closed out (error split kept, `TimeBounds` gone).
jaemk
force-pushed
the
260720.pre-3.0-additive-parity
branch
from
July 21, 2026 01:55
b2aa189 to
ca91f18
Compare
…cache_try_get_or_set_with`, `retain` on map stores
jaemk
force-pushed
the
260720.pre-3.0-additive-parity
branch
from
July 21, 2026 12:40
ca91f18 to
ffbecc1
Compare
jaemk
added a commit
that referenced
this pull request
Jul 24, 2026
jaemk
added a commit
that referenced
this pull request
Jul 25, 2026
…ocsrs badges, doc and spec corrections (#296) - `#[cached]` on a non-`Clone` return type now emits a `Clone`-bound error spanned at the return type (a compile-time assertion on the cached value type, including `Return<T>` under `with_cached_flag`), ahead of the opaque errors from the generated internals. Trybuild tests cover the plain and `with_cached_flag` negative cases plus a generic-function positive case. - add the missing `doc(cfg(feature = "async_core"))` badges on the `CachedGetOrSetAsync` / `ConcurrentCachedAsync` impls for the in-memory and sharded stores and `HashMap`, so docs.rs marks them feature-gated. - correct the changelog and `specs/store-lru.md` claim that `UnboundCache` has no `retain` (it shipped in #294); document the `UnboundCache` semantics (predicate filter, fires `on_evict`, no eviction counter). - migration guides: fix the `cache_peek_with_expiry_status` sibling name, reword the rc-era no-arg builder note, and add human-guide sections for `CacheTtl`/`CacheEvict` removal from concurrent stores and the redis empty-prefix `InvalidValue` rejection. - specs: add LRU-5/TTL-5/EXPIRE-6 covering `iter_order`/`value_order`/`CacheValue`; mark design 0020 Declined in the index. - document the lookup-key difference between the trait families (`&Q where K: Borrow<Q>` on `Cached` vs `&K` on `ConcurrentCached`) in the lib.rs comparison docs; README regenerated.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Additive API parity ahead of 3.0.0 final. Stacked on #293.
peek(&self, &K) -> Option<V>to all six sharded stores: clone of the live value, no recency/TTL/metrics effects, no lazy removal of expired entries.Builder::new()to the 13 in-memory and sharded builders, equivalent to the store's::builder()(parity with the IO builders' public constructors).CachedExt::capacity/evictionsandConcurrentCachedExt::len/is_empty/hits/misses/capacity/evictionsaliases.ConcurrentCached::cache_try_get_or_set_withandConcurrentCachedAsync::async_cache_try_get_or_set_with: fallible-init get-or-set returningResult<Result<V, E>, Self::Error>(store error outer, closure error inner; nothing stored on closureErr).retain(keep)toTtlCache/ExpiringCache; expired entries are dropped regardless of the predicate.UnboundCachegets noretain: it has no eviction dimension backing the operation.TtlSortedCache::capacity()and the missingdoc(alias = "capacity")on its builder'smax_size.AsyncRedisCachelisting under the synccache_containsand a garbled parenthetical.tests/v3_additive_parity.rscovering all of the above.