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
At the moment, the user can subscribe to incoming messages by passing a MessageHandler, a default implementation for static Functions is provided, and the user can implement the trait if (s)he needs to.
It could be a good idea to grasp inspirations from other crates to know how such a pattern is handled. Giving the user an infinite iterator over messages looks (naively) like a possibility, but how do such "infinite, blocking iterators" work?
At the moment, the user can subscribe to incoming messages by passing a
MessageHandler
, a default implementation for static Functions is provided, and the user can implement the trait if (s)he needs to.It could be a good idea to grasp inspirations from other crates to know how such a pattern is handled. Giving the user an infinite iterator over messages looks (naively) like a possibility, but how do such "infinite, blocking iterators" work?
References:
May be an interesting approach:
https://github.com/rust-lang/rfcs/blob/master/text/2033-experimental-coroutines.md
The text was updated successfully, but these errors were encountered: