Peter Hall

I agree about adding a type parameter for the message type. One slightly awkward thing is how ZMQ treats topics. It is reasonable for a topic to be of a...

It definitely needs some thought to get the right balance between simplicity, safety and versatility. One possibility is to have a sensible default for the topic, e.g. `Subscribe`. This seems...

We could also just make the decision to only support topics which are sent as a separate message part. I have no idea how common the other patterns are in...

For now, I'm using int because I just need to get it working.

`UnsafeFn` sounds like an unsound abstraction. When using an `unsafe` function, it's your responsibility to read documentation and understand all assumptions and invariants that need to be satisfied. This cannot...

> I understand the argument against `Unsafe Fn`. But wouldn't this apply to `unsafe fn` pointers too? Yes, I would say so.

> I don't know how to support higher-order signatures while at the same time > preventing multiple call signatures for a type other than keeping Fn* > perma-unstable. > Changing...

I'm experiencing this in the latest (Feb 2020) build. I am unable to get past the splash screen. Pixel 2.

> 1. The lower and upper bounds of the set size hint are decremented with each consumed item to ensure that the user's estimate of the size bounds are adjusted...

That's true. There is no reason to use the method if you don't need it.