think im turning into a computer because ive been reading the rust book for the past two days and now im dreaming in code
by user Koffeekake on community discord server
Might be good to have this as the quote of the week? It sends a good message IMHO.
(Also, @ZiCog I found you're quote funny too but I agree with josh)
Found a great quote:
I love Rust like I love Dark Souls.
It's difficult, but fair. I can not praise enough the software developers that realize proper errors are vastly superior to extensive docs.
And it's worth noting that we have fairly extensive docs as well, so it's not an either-or situation.
It's the typical "pick all 3" solution that the Rust team loves to find.
You are correct! In my experience learning Rust, more often than not, the error messages were enough to correct the code and make it compile (well, after lifetimes "clicked" in my head), and then I would go to the docs for those error codes to go deeper into the problem, concepts and different (but equivalent) examples.
The purpose of pin is to have unsafe code in one crate make guarantees to unsafe code in another crate, possibly with non-unsafe code in the middle
This one's a bit old, but it relates to my current situation very much:
That’s one of my general complaints with
serde
: it’s either super convenient and exactly what you want, or it’s a screaming nightmare. There’s no in-between.
- DanielKeep, Catchall variant in Serde
Many thanks for all your answers, I am very pleased to have a chat with you.
@thomas-hugel, after asking a question about green threads and getting nice and informative replies.
I'd like to include the whole quote, but it's two paragraphs. This is the best takeaway, IMHO.
But then again, what isn't hard as a beginner?
Brilliant characterization by analogy!
Memoize function without cloning - #2 by red75prime
Most functional languages use garbage collection, so memory management is not a concern there. In Rust we need to do something explicitly.
Explaining why the borrow checker is complaining and how to deal with it.
A concise description of what I find compelling about Rust's approach to correctness.
One problem I've had, in general and not with just Rust, is that people can find a way to do anything with anything. I've seen people do some horrific stuff with their hammers just to prove they don't need a screwdriver.
[SIMD is] the perfect knife edge between awe and expletives.
-- Stephen Merity @ Smerity.com: An introduction to SIMD and ISPC in Rust
That's the way I feel about the borrow checker.
Rust enables belligerent refactoring – making dramatic changes and then working with the compiler to bring the project back to a working state.
So true : https://blog.knoldus.com/some-extensive-projects-working-with-rust/