@rustaceans

Tokio!

It's 'static + multithreaded-by-default requirement has created the myth that async #Rust is inherently difficult.

People should use `smol` more - here's why:

#Async Rust can be a pleasure to work with (without `Send + Sync + 'static`) - by Evan Schwartz:

https://emschwartz.me/async-rust-can-be-a-pleasure-to-work-with-without-send-sync-static/

https://floss.social/@janriemer/114681713674697800

#smol #RustLang #Asynchronous #AsyncRust

Ok, @calisti, I _think_, I've figured it out now (please read until the later parts of the toots as they are the most important)!🤓

Tldr; The `or` or `race` operators _on their own_ are not suitable for cancelling streams! One needs a `StopToken` or enum value _within the stream_ that signals cancellation/allows for short-circuiting.

1/?

#Rust #RustLang #AsyncRust #Async

Second: Pinning helpers!

When doing async #Rust, there will be a point, where you'll get the ominous "Doesn't implement Unpin" error and "You need to pin your value".

First, learn about Pinning:
https://doc.rust-lang.org/std/pin/

Like, _really_ learn and understand it:
https://fasterthanli.me/articles/pin-and-suffering

And then use smol's pin! macro and the `pin_project` crate:
https://docs.rs/pin-project/latest/pin_project/

I might continue this thread with more insights I gain during this little project - stay tuned! 🙂

4/4?

#RustLang #AsyncRust