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
I have encountered an issue related to the wait_event method in the Stream struct. It appears that when the method is called, it consumes the Event object, resulting in the event being dropped each time.
Considering that generating events is not cheap, I would like to understand the rationale behind passing ownership of the event and dropping it on each wait. Is there a specific reason for not passing an event reference instead, allowing the event to be reused?
Thanks!
The text was updated successfully, but these errors were encountered:
I have encountered an issue related to the wait_event method in the Stream struct. It appears that when the method is called, it consumes the Event object, resulting in the event being dropped each time.
Considering that generating events is not cheap, I would like to understand the rationale behind passing ownership of the event and dropping it on each wait. Is there a specific reason for not passing an event reference instead, allowing the event to be reused?
Thanks!
The text was updated successfully, but these errors were encountered: