Marc Gravell

> I can't think of any other common collection which is a struct otherwise. If we're just talking about consuming: `ArraySegment`, `[ReadOnly]Memory` and possibly `[ReadOnly]Span`; but for read/write: not so...

The problem here is: the maintainers aren't AWS users. We don't know how AWS topologies are implemented, and we don't have an endpoint to test against, and I have no...

You can move the GetDatabase() outside too: var db = client.GetDatabase(); for (int i = 0; i < 200000; i++) {

This doesn't seem to be ACL related to me. If it was working, it should continue working. This seems more likely to be simply fallout due to a cluster topology...

And as I intimated earlier: if the library can help here, we can tweak it. I don't know if we explicitly react to `-READONLY` and interpret it as a config...

Fair point. I'll think about how we can re-expose this. On Mon, 8 Oct 2018, 05:39 BrennanConroy, wrote: > With the introduction of ChannelMessageQueue Subscribe(...) and the async > version,...

I can confirm this isn't something we've had chance to look into yet, but it is on our roadmap - and as it happens, I was rewriting our own internal...

I do not have a specific suggestion there for now. As I say: it is on our list to look at. For other things for now: you'd have to look....

Because everything requires time and effort, and the more code we add, the more code we need to support. The library is *massively* downloaded, and we get zero paid hours...

As discussed in our [Stack Overflow conversation here](https://stackoverflow.com/a/66965066/23354), this will require library changes, to (reliably) get the `CLIENT ID` as part of the initial connection handshake. They're not huge or...