Tokio 1.0 – async runtime for Rust

Re:Tokio 1.0 – async runtime for Rust by sanxiyn on Wednesday December 23, 2020 @05:25PM (#25522987)

reqwest provides a blocking API, but reqwest also always depends on Tokio. A blocking API doesn't help when I don't want Tokio in my dependency tree at all.

I am using isahc, but that also doesn't help when (say) Rusoto AWS library pulls reqwest pulls Tokio pulls async.

[ Parent | on HN ]

Re:Tokio 1.0 – async runtime for Rust by fastball on Wednesday December 23, 2020 @05:46PM (#25523167)

Doesn't sound like a problem with async, just sounds like you disagreeing about what good deps for your deps are.

[ Parent | on HN ]

Re:Tokio 1.0 – async runtime for Rust by eropple on Wednesday December 23, 2020 @07:27PM (#25523920)

Can you explain exactly what that library using Tokio internally exposes to you that's a problem? Because, as written, this sounds like a religious argument.

[ Parent | on HN ]

Re:Tokio 1.0 – async runtime for Rust by therein on Wednesday December 23, 2020 @09:10PM (#25524459)

If you need to use (for the sake of the example) Rusoto, since it is based on tokio, you'll need to set up the Tokio executor or at least add a macro to your main for this to be done for you. I believe Rusoto actually would take care of this for you if you haven't done it yourself however friction arises when you were already using a different version of tokio and Rusoto is built against another.

Basically, it isn't entirely opaque to you how it is handled.

[ Parent | on HN ]

Re:Tokio 1.0 – async runtime for Rust by eropple on Wednesday December 23, 2020 @11:59PM (#25525175)

Gotcha, makes sense. Thanks!

[ Parent | on HN ]