You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thanks for your work on this crate.
I find recv_deadline on a channel a bit ambiguous when we pass an Instant that is in the past. This behavior isn't documented and, in my first intuition was: it will not even try to recv as the deadline is already pass. After a test it shows me that even if the deadline is in the past but there is already a message in the channel he will be received.
Do you think the behavior should change or is it possible to document it ?
The text was updated successfully, but these errors were encountered:
"deadline" relates to whether or not to wait for a message for how long, and I think it is reasonable to receive it if the message is immediately available.
I think it is reasonable to document the behavior.
Hello,
Thanks for your work on this crate.
I find
recv_deadline
on a channel a bit ambiguous when we pass anInstant
that is in the past. This behavior isn't documented and, in my first intuition was: it will not even try torecv
as the deadline is already pass. After a test it shows me that even if the deadline is in the past but there is already a message in the channel he will be received.Do you think the behavior should change or is it possible to document it ?
The text was updated successfully, but these errors were encountered: