Curious on your thoughts: on public interfaces I normally like returning a wrapper with functions to access the channels instead of returning raw channels. Does that feel too abstracty for this? I could feel it being slightly verbose needing to always store two channels.

It's a good instinct, and I think it depends on how we expect it to be used. In this case, I'm imagining that we will have an object that "glues" the Coordinate() call to the drpc Stream.

e.g.

type coordinateStreamer struct {
    stream proto.DRPCStream_Coordinate
    reqs chan<- *proto.CoordinateRequests
    resps <-chan *proto.CoordinateResponse
}

And this thing will have very simple methods that copy from the channels into the stream and vice versa.

Thus, I'm kinda already planning to wrap them up in a struct as soon as they are returned, so putting them together in a wrapper just means I have to unwrap.

Makes sense 👍