—/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
More like “boring is good” kind of people no surprises whatsoever
“The cost of zero-cost abstractions”. Looks like a title for some sci-fi…
Writing code in Rust makes me feel like I have an obligation to make code as fast as possible in a way other languages don’t, just by surfacing the costs better. Sometimes I need to remind myself that actually it’s fast enough already.
I used to think of programs as execution flowing and think about what the CPU is doing. As I moved to rust I started thinking a lot more about memory: how the data was laid out in memory, and how ownership of different parts of memory is given to [different parts of the program] at run time.
– Oliver Gould
(slightly edited from spoken to written style)
Time of the quote: https://youtu.be/FYGS2q1bljE?t=280
I like that one since it’s in some ways a modern take on a classic:
Show me your flowcharts and conceal your tables, and I shall continue to be mystified. Show me your tables, and I won’t usually need your flowcharts; they’ll be obvious.
– Fred Brooks, The Mythical Man-Month (1975)
why doesn’t 'static, the largest lifetime, not simply eat all the others
'static is biggest but actually,, weakest of lifetimes, becuase it is subtype of every lifetime
'static is big soft friend
pls love and protect it
This is also an incredibly important shift when trying to write performant software. See also this great C++ talk: https://youtu.be/rX0ItVEVjHc
apparently I wrote Building Git to explain a complex problem to rust devs who could then help me build it in rust