i think the best way to propagate connection RESETs is to stick a first-class notion of "channel closed with error" into tricky-pipe.
also, it would be nice if an attempt to send a message through a DeserSender that results in a deserialize error also sent the deserialize error to the receiver, as well as returning it to the sender...
i think the best way to propagate connection RESETs is to stick a first-class notion of "channel closed with error" into
tricky-pipe
.also, it would be nice if an attempt to send a message through a
DeserSender
that results in a deserialize error also sent the deserialize error to the receiver, as well as returning it to the sender...Originally posted by @hawkw in https://github.com/tosc-rs/mgnp/issues/23#issuecomment-1807192999