Rust

7269 readers

29 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 2 years ago

MODERATORS

snowe@programming.dev

Ategon@programming.dev

EdTheLegendary@programming.dev

kahnclusions@programming.dev

torcherist@programming.dev

How I Have Fun With Rust - Matheus Richard (thoughtbot.com)

submitted 2 years ago by snaggen@programming.dev to c/rust@programming.dev

6 comments fedilink hide all child comments

top 6 comments

sorted by: hot top controversial new old

[–] tatterdemalion@programming.dev 9 points 2 years ago* (last edited 2 years ago) (1 children)

"how to write sloppy rust code and squander most of the advantages of the language"

Only half serious. But I think really the only point that I agree with is taking the easy way out with the borrow checker. I mean, at least try to borrow when it's idiomatic, but if you get frustrated, clone (or move) instead.

Error handling when done well is not much harder than unwrapping everything, and you get many advantages. Learn to use thiserror for your library crates and anyhow for executables.

I also agree that you should avoid unsafe 99% of the time. If you think you need it, you probably don't.

[–] snaggen@programming.dev 5 points 2 years ago

I see this post as an advice to learn gradually, and to write sloppy but painless code initially. Then when you have the basics, you can add the more idiomatic and tricky parts.

[–] asdfasdfasdf@lemmy.world 2 points 2 years ago (1 children)

I agree with 99%, but not sure I see how async is a "fancy feature". When you're writing async code, async is boring and normal. I guess if you are writing programs that don't need to be concurrent it's fine to use sync variants of stuff.

[–] snaggen@programming.dev 4 points 2 years ago (1 children)

Well, when you write async code, you may suddenly find your self needing to implement AsynRead or something similar. Suddenly you have to use pin, and understand how async worksbunder the hood. So, while I agree that async is not something fancy, it will possibly throw you in some quite advanced territory. The part I'm not sure I agree with is skipping the error handling. But I see what the authors intention is, to keep hairy stuff out of the way while learning the basics.

[–] asdfasdfasdf@lemmy.world 0 points 2 years ago* (last edited 2 years 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 1 points 2 years 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.