Moka-py

Fixed

- Fixed a bug in `sync::Cache` and `sync::SegmentedCache` where memory usage kept
increasing when the eviction listener was set with the `Immediate` delivery mode.
([295][gh-pull-0295])

Bumped the minimum supported Rust version (MSRV) to 1.65 (Nov 3, 2022).
([275][gh-pull-0275])

Removed

- Removed `num_cpus` crate from the dependency. ([277][gh-pull-0277])

Changed

- Refactored internal methods of the concurrent hash table to reduce compile times.
([265][gh-pull-0265], by [Swatinem][gh-Swatinem])

Fixed

- Fixed occasional panic in internal `FrequencySketch` in debug build.
([272][gh-pull-0272])

Added

- Added some example programs to the `examples` directory. ([268][gh-pull-0268], by
[peter-scholtens][gh-peter-scholtens])

Added

- Added support for per-entry expiration ([248][gh-pull-0248]):
- In addition to the existing TTL and TTI (time-to-idle) expiration times that
apply to all entries in the cache, the `sync` and `future` caches can now allow
different expiration times for individual entries.
- Added the `remove` method to the `sync` and `future` caches
([255](gh-issue-0255)):
- Like the `invalidate` method, this method discards any cached value for the
key, but returns a clone of the value.

Fixed

- Fixed the caches mutating a deque node through a `NonNull` pointer derived from a
shared reference. ([259][gh-pull-0259])

Removed

- Removed `unsync` cache that was marked as deprecated in [v0.10.0](version-0100).

Bumped the minimum supported Rust version (MSRV) to 1.60 (Apr 7, 2022).
([252][gh-issue-0252])

Changed

- Upgraded `quanta` crate to v0.11.0. ([251][gh-pull-0251])
- This resolved "[RUSTSEC-2020-0168]: `mach` is unmaintained"
([243][gh-issue-0243]) by replacing `mach` with `mach2`.
- `quanta` v0.11.0's MSRV is 1.60, so we also bumped the MSRV of Moka to 1.60.

Fixed

- Fixed a bug that `future` cache's `blocking().invalidate(key)` method does not
trigger the eviction listener. ([242][gh-issue-0242])

Changed

- Now `sync` and `future` caches will not cache anything when the max capacity is set
to zero ([230][gh-issue-0230]):
- Previously, they would cache some entries for short time (< 0.5 secs) even
though the max capacity is zero.