Async Rust is amazing, but not flawless; async bloat is an issue. In this blog, @diondokter explains the causes of async bloat, and some workarounds: https://tweedegolf.nl/en/blog/235/debloat-your-async-rust
Async Rust is amazing, but not flawless; async bloat is an issue. In this blog, @diondokter explains the causes of async bloat, and some workarounds: https://tweedegolf.nl/en/blog/235/debloat-your-async-rust
@tweedegolf @diondokter
Cool, thank you!
I've already been doing trivial pass-through without realizing that I should actually be doing this. It simply appeared more elegant to me.
I've had issues with error handling, but thanks to your post, I looked at the futures crate more closely and have figured it out:
```rust
future::ready(result).err_into().and_then(fn_returning_future)
```