directional channel for Channel.NotifyReturn() about amqp HOT 2 CLOSED

A send only chan communicates the intent better, but makes it impossible to return the user supplied parameter in this API as it's not possible to cast directional channels to the other side. The idea with returning the caller's param is to make it clear at the call site that the chan is only valid when having registered with NotifyReturn and reduce one intermediate variable.

go processReturn(channel.NotifyReturn(make(chan Return, 1)))

Alternatively, accepting a send only channel does make the intent clearer, though the code longer with even more stutter var string_ string = strings.NewString().

returns := make(chan Return, 1)
channel.NotifyReturn(returns)
go processReturn(returns)

For strictness sake, removing the return value and accepting a directional channel could be better but I'm not certain how much value that'd give as the call-site would need a bidirectional channel to be useful.

Do you have a concrete example where an API with a directional channel would resolve an ambiguous usage for the caller?

from amqp.

Feel free to reopen if you have a compelling case on the call site to change the API.

from amqp.