this post was submitted on 22 Dec 2023
28 points (91.2% liked)

Rust

5999 readers
64 users here now

Welcome to the Rust community! This is a place to discuss about the Rust programming language.

Wormhole

!performance@programming.dev

Credits

  • The icon is a modified version of the official rust logo (changing the colors to a gradient and black background)

founded 1 year ago
MODERATORS
snowe@programming.dev
Ategon@programming.dev
EdTheLegendary@programming.dev
kahnclusions@programming.dev
torcherist@programming.dev
28
How I Have Fun With Rust - Matheus Richard (thoughtbot.com)
submitted 11 months ago by snaggen@programming.dev to c/rust@programming.dev
8 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[โ€“] asdfasdfasdf@lemmy.world 0 points 10 months ago* (last edited 10 months ago) (1 children)

I've been writing async Rust professionally for 5 years and never needed to implement AsyncRead, or even Future directly. I've only used Pin for working with the async_stream macro. That stuff is very low level and probably would never be encountered by the vast majority of async users.

[โ€“] snaggen@programming.dev 2 points 10 months ago

Well, you don't need it until you suddenly do. But I guess it might be very different for different users depending on your use case. I have found myself needing to go low level for async a few times, and I don't think I'm doing very strange things.