Dmitry Verkhoturov

I just wanted to let you know that I plan to work on this issue shortly. Current endpoint: ```go // GET /find?site=siteID&url=post-url&format=[tree|plain]&sort=[+/-time|+/-score|+/-controversy]&view=[user|all]&since=unix_ts_msec // find comments for the given post. Returns...

#1699 adds backend support for solving that issue. If someone here has the skills to do it, feel free to review and leave your comments.

I've had time to think about it, and now I think it's better to make it simply a "Close" method rather than destructor magic. Using a destructor in Go feels...

Please see https://github.com/hashicorp/golang-lru/pull/116#discussion_r1286163423 for the reasons I removed it, it was a requirement for merging as I understood it.

Closing as non-reproducible for now. Feel free to reopen if you'll see such symptoms ever again.

`git rebase upstream/master` is what you need to do in your branch.

I'll check it this weekend. Adding the per-item expiration is not possible within the current interfaces, but overall, it should be possible to merge these two in the way it's...

I can integrate an expirable cache with `simplelru.LRU` as I did in this MR, but it becomes thread-safe which is a breaking change: it's impossible to make an expirable cache...

Values are stored as-is and changing the mutable value will change all its references. You can store multiple pointers to the same object, but there is no magic in this...

Can you please post how the printed resume looks like? Here is mine, I think that's how LinuxBozo designed it to be, e.g. without foto and with less details: https://terrty.net/cv/