-
Notifications
You must be signed in to change notification settings - Fork 13
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
feat: add support for tokio #52
Conversation
Allows configuration of either tokio or async-std. Drops support for `socks5` with `async-std`, as the underlying library `fast-sockst5` has done so in the latest release.
So how are we going to use async-smtp in delta chat now? We use socks5 there. |
I am working on switching DC to tokio |
Why? Not against it, just don't know what's the difference and first time I hear you are working on it. Seems most libraries (sqlx, async-native-tls) support multiple runtimes now. fast-socks5 PR for reference: dizda/fast-socks5#9 |
} | ||
} | ||
|
||
/// Execute io operations with an optional timeout using. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Copy-pasted comment: "using" what?
depends on - [ ] chatmail/async-smtp#52 - [ ] chatmail/async-imap#21
depends on - [ ] chatmail/async-smtp#52 - [ ] chatmail/async-imap#21
depends on - [ ] chatmail/async-smtp#52 - [ ] chatmail/async-imap#21
depends on - [ ] chatmail/async-smtp#52 - [ ] chatmail/async-imap#21
Allows configuration of either tokio or async-std.
Drops support for
socks5
withasync-std
, as the underlying libraryfast-socks5
has done so in the latest release.Closes #13