LousyBeggar, on reddit
Nobody contributed. Rust started writing itself to avoid human bugs.
Asimov needs a 4th law to
– rat9988 and CUViper on Reddit.
– Rust’s ownership is difficult.
– Yes, ownership is difficult. For such a difficult thing, you (are going to) ever check by hand rather than having machine do it for you.
– @Cryolite on Twitter (Japanese)
normally-aspirated::<fish> on the (unofficial) community discord:
Rust is OOP
Ownership Oriented Programming
“all the ergonomic improvements in rust 2018 are really messing up my book that consists entirely of running face-first into compiler errors so i can explain concepts.” – Alexis Beingessner, author of “Learning Rust With Entirely Too Many Linked Lists”
C++ prevents “thing without pointer” and Rust prevents “pointer without thing”
I quite liked TomP’s answer:
One major difference is that Ada was created at a time when most military computers were single-core with in-order sequential execution and no cache. Although limited SIMD existed, any other concurrency was very coarse-grained. That’s the underlying execution model for C, Pascal, C++, etc.
Rust was created to address the complexity of multi-core processors with multi-level cache hierarchies where computational efficiency may require much concurrency. In my experience few humans are capable of error-free design and implementation of highly-concurrent systems unless they employ tooling that flags their errors in conceptualization or implementation.
—/u/casual-cryptarch on explaining traits and references at the same time
Yes, Markdown is like Frankenstein’s monster before applying electricity, and Org-mode is the monster after applying electricity.
(not really a quote about Rust, but I found it pretty enjoyable nonetheless)
A compile_fail test that fails to fail to compile is also a failure.
The trybuild README.
Yes, this adds to Rust’s “wierdness budget”, but this is doing it for the right reason: discovering a way to solve a problem that many programming languages have, but few have really tackled.
await syntax (on internals)
The big gorilla 3D game framework. Apparently it actually works.
Never play drinking games with the rust compiler. It will destroy you and show you how sorry of a developer you are!
Just the presence of well integrated Algebraic Data Types (ADTs) makes an incredible amount of difference. They are used to represent errors in a meaningful and easy to understand way (
Result<T>), are used to show that a function may or may not return a meaningful value without needing a garbage value (
Option<T>), and the optional case can even be used to wrap a null pointer scenario in a safe way (
Option<Ref<T>>being the closest to a literal translation I think).
That’s just one small feature that permeates the language. Whatever the opposite of a death-of-a-thousand-cuts is, Rust has it.
Rust attracts people who like challenges.
He’s not pointing in the right direction, but the direction itself is calling!
Sure, but isn’t it more likely that the person who wrote the Rustonomicon, whoever they are, is just a huge dingus‽
Bonus points for the interrobang.
Note that the HTML syntax is a language almost, but not quite, entirely unlike XML.
– html5ever README