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
The TLS example depends on async-native-tls, which has async-std as a dependency. I'm not sure how compatible smol is with libraries based on async-std, which is a whole other runtime. This also raises the question of whether futures-lite crates are compatible with futures-based crates, since the two use different Futures libraries. Even if compatibility isn't an issue, having async-std alongside smol will blow up compile times, which defeats the purpose of using smol in the first place. I suggest we use async_tls instead, since it doesn't depend on async-std or futures.
The text was updated successfully, but these errors were encountered:
The TLS example depends on
async-native-tls
, which hasasync-std
as a dependency. I'm not sure how compatiblesmol
is with libraries based onasync-std
, which is a whole other runtime. This also raises the question of whetherfutures-lite
crates are compatible withfutures
-based crates, since the two use differentFutures
libraries. Even if compatibility isn't an issue, havingasync-std
alongsidesmol
will blow up compile times, which defeats the purpose of usingsmol
in the first place. I suggest we useasync_tls
instead, since it doesn't depend onasync-std
orfutures
.The text was updated successfully, but these errors were encountered: