Karl Seguin

Short: I don't feel strongly about it, no. Feel free to close. Long: Not related specifically to this issue, but in general I've found the file source with small files...

for what it's worth, I cloned the project and pushed an updated npm as "hashlib2": http://search.npmjs.org/#/hashlib2

When an item is added (through set/replace/fetch), it's automatically promoted. If you're asking for a special method, like `c.Promote(key)` I think you can just do: ``` _ = c.Get(key) ```...

Are you ok with the cache being unusable once `Stop` is called? Is panic'ing a little extreme or acceptable? Consider: https://github.com/karlseguin/ccache/commit/bfa769c6b6c794afa640d7259ebc270c7da037a7

There's no special configuration. You could increase the # of buckets to 32 or even 64 and, if you have long TTLs of oft-fetched items (and you're OK with occasionally...

Every instance of ccache has 1 worker threads which is responsible for maintaining the cache. This simplifies and minimizes the amount and type of locking that needs to take place....

Good idea. I'll try to get to it at some point, but I'd also accept a PR in the meantime.

I'm happy to try to fix these. I believe I've fixed the intermittent issue that you were seeing. One of the fundamental problems with ccache tests is that many ccache...

https://github.com/karlseguin/ccache/pull/61 Stop no longer works by closing promotable. Instead, it uses a control message (control messages are relatively new, which I guess is why I didn't use it in the...

Took another stab at this. Clean up control some. Don't rely on closing channels to stop. https://github.com/karlseguin/ccache/pull/63