hp_hovercraft84

6 ms·

1. 1.▲
   by hp_hovercraft84 1y ago

   Good call, but I think I would like to ensure it remains thread-safe as @store is a hash. Although I will consider something like this in a future update. Thanks!
2. 2.▲
   by hp_hovercraft84 1y ago

   This is why I love working with Ruby!
3. 3.▲
   by hp_hovercraft84 1y ago

   That's actually a really good idea! I'll definitely consider this in a future update. Thanks!
4. 4.▲
   by hp_hovercraft84 1y ago

   Good question. I built this gem because I needed a few things that Rails.cache (and Redis) didn’t quite fit: - Local and zero-dependency. It caches per object in memory, so no Redis setup, no serialization, no network latency. -Isolated and
5. 5.▲
   by hp_hovercraft84 1y ago

   As in identify where the source code is in the README?
6. 6.▲
   by hp_hovercraft84 1y ago

   Thanks for the feedback! That's a very good point, I'll update the gem and let it bubble up.
7. 7.▲
   Show HN: I built a Ruby gem that handles memoization with a ttl(github.com)

   48 points by hp_hovercraft84 1y ago|26 comments
8. 8.▲
   by hp_hovercraft84 4y ago

   No info about how the product works, immediate close.