3 comments

  • virtualritz2 hours ago
    Should be checked against official Rust API naming guidelines. LrukCache, not LRUKCache etc.<p><a href="https:&#x2F;&#x2F;rust-lang.github.io&#x2F;api-guidelines&#x2F;naming.html#casing-conforms-to-rfc-430-c-case" rel="nofollow">https:&#x2F;&#x2F;rust-lang.github.io&#x2F;api-guidelines&#x2F;naming.html#casin...</a>
    • yccs271 hour ago
      Thanks for the link, nice to see the informal conventions spelled out like this!
    • failsafe2 hours ago
      ah, gad damn it. cheers though :P
  • fyrn_2 hours ago
    Would love to see benchmarks vs competition considering the high performance claim. Foyer is another rust hybrid cache, and quick-cache is the fastest in-memory impl I&#x27;m aware of.<p>Sane defaults and easy of setting a memory limit are two other things I look for in caches.
  • carlmr3 hours ago
    On your example, without reading into the implementation, I&#x27;m wondering if the comment is wrong, or if the comment is telling us about a hidden default, but then what does the 2 mean.<p><pre><code> &#x2F;&#x2F; Create an LRU cache with a capacity of 100 entries let mut cache = LRUKCache::new(2); </code></pre> Why 100? Why not 2?
    • failsafe3 hours ago
      derp, It should be LRU instead of LRU-K.