Jerome Froelich

Hey @felipou 👋 > Anyway, I'm thinking about creating a pull request implementing these features, would that be a welcomed feature? Definitely! This sounds like a broadly useful feature and,...

We're also running into this issue and I'd be happy to put up a pull request to address it. From what I can tell, the issue is because the write...

@AliceProxy sorry for the direct ping, just curious if you have any thoughts on this issue?

Hey @behzadnouri 👋 This is awesome! I would definitely be open to merging once the API is finished – then users of the library can choose which implementation suits them...

@timvisee thanks for looking into this! I'll close this PR in favor of your newer PR #25.

Said in another way, Item 1 is meant to address the use case where we have services running in different zones (think datacenters, or AZs) that talk to the same...

I'm also in favor of traditional paths for the keys. However, I think prefixing the keys with `kv/` would be advantageous since it would allow us to easily distinguish keys...

O, I see, I didn't realize you wanted to keep `kv` as a namespace. Yea I like that idea, and if `kv` is now a namespace,`zone` and `environment` should take...

What do you think of following the example of [drwmutex](https://github.com/jonhoo/drwmutex) to make the pool per-CPU instead of per-P so we don't have to call into the runtime?

Did some [benchmarks](https://github.com/jeromefroe/golang_benchmarks#pool-put-non-interface) and there didn't seem to be a significant difference in execution time between using slices versus pointers to slices: ``` Benchmark Name|Iterations|Per-Iteration|Bytes Allocated per Operation|Allocations per Operation...