-
Notifications
You must be signed in to change notification settings - Fork 121
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove "sync" feature(s) #145
Comments
Do you have one to suggest? |
Unfortunately not. Re-implementing the sync client(s) by reusing common parts from |
I was starting to build up a library on top of this crate and started to use traits. The code started getting more complex than it needed to be so I tried out the sync version of the library only to discover its also creating creating and managing its own runtimes. Maybe theres an alternate approach here where a runtime handle could be passed into the sync of this library, or one could be discovered. This is the error I was running into when trying to connect:
My goal here was to asynchronously query multiple servers and for simplicity with the traits I was going to use sync inside each thread to query the one device. |
I have downstream library code that depends on this crate. |
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: