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
Bundling an opinionated synchronous API wrapper around the native, asynchronous API is unfortunate and wrong. It only causes trouble and misunderstandings. I recommend to remove it before releasing version 1.0.
If users need synchronous communication they should use a different library.
The text was updated successfully, but these errors were encountered:
If users need synchronous communication they should use a different library.
Do you have one to suggest?
Unfortunately not.
Re-implementing the sync client(s) by reusing common parts from frame and codec but without the unnecessary Frankenstein-ean loop through the Tokio runtime would be the path forward.
Bundling an opinionated synchronous API wrapper around the native, asynchronous API is unfortunate and wrong. It only causes trouble and misunderstandings. I recommend to remove it before releasing version 1.0.
If users need synchronous communication they should use a different library.
The text was updated successfully, but these errors were encountered: