ttlcache VS golang-set

And the library that will be used to cache our application data is ttlcache, because it is easy to use and has an immensely intuitive API.

My favourite form of caching is one that expires auto-magically https://github.com/ReneKroon/ttlcache

If it were true, there wouldn't be any 3rd-party libs for Go and everybody used just the stdlib. For instance, if you need a set, you can use https://github.com/deckarep/golang-set . Of course, you can do it with the stdlib with map, but if you don't want to do that, use golang-set . I think Python has a much larger stdlib and yet, Python has tons of 3rd-party packages.

golang-set is a set implementation used by docker, ethereum and others. 2.8k stars on GitHub. Pretty popular project. Not sure if it counts as major. https://github.com/deckarep/golang-set

Why not look at something like https://github.com/deckarep/golang-set ?

It depends on the level of abstraction you're addressing. One level may be "i need to store things with a quick search function", another may be "i need a storage of ordered names and expiry date for things", etc until you get to "I need a binary tree which orders by comparable types".

Where you split that process as a separate library you either decide to write or reuse - that becomes the problem to solve. A set implementation may be a problem to solve: https://github.com/deckarep/golang-set A btree may be a problem to solve: https://gitlab.com/cznic/b/-/tree/master/v2

This pre-release only exists on the generics branch at: https://github.com/deckarep/golang-set/tree/generics. Eventually this release would be tagged with a 2.0 release tag name.