SizedCache was not preventing duplicate keys from existing
in the internal ordering list. When SizedCache::cache_set
was called with an existing key, the key would still be
prepended onto the ordering-list. When it came time for a
duplicate key to be evicted, it would be missing from the
hashmap and cause a panic.
orderinglist. When SizedCache::cache_set was called with an existing key, the key would still be prepended onto the ordering-list. When it came time for a duplicate key to be evicted, it would be missing from the hashmap and cause a panic.