TWiR quote of the week

The big gorilla 3D game framework. Apparently it actually works.

SimonHeath on Amethyst

1 Like

Never play drinking games with the rust compiler. It will destroy you and show you how sorry of a developer you are!

1 Like

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.

tomcatfish on “… how (Rust) takes basic concepts from low to high level without bothering me or killing performance…”

6 Likes

Rust attracts people who like challenges.

3 Likes

He’s not pointing in the right direction, but the direction itself is calling!

6 Likes

Sure, but isn’t it more likely that the person who wrote the Rustonomicon, whoever they are, is just a huge dingus‽

- /u/kibwen in response to the author of the Rustonomicon

Bonus points for the interrobang.

3 Likes

Note that the HTML syntax is a language almost, but not quite, entirely unlike XML.
html5ever README

8 Likes

More like “boring is good” kind of people :smiley: no surprises whatsoever

“The cost of zero-cost abstractions”. Looks like a title for some sci-fi…

3 Likes

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.

http://thume.ca/2019/04/18/writing-a-compiler-in-rust/

15 Likes

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)

https://www.youtube.com/watch?v=FYGS2q1bljE

Time of the quote: https://youtu.be/FYGS2q1bljE?t=280

8 Likes

– zeroexcuses
from https://users.rust-lang.org/t/can-a-struct-that-own-an-instance-of-a-struct-also-maintain-a-reference-to-this-instance-without-a-generic-lifetime/28542/9

6 Likes

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)

12 Likes

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

7 Likes

This is also an incredibly important shift when trying to write performant software. See also this great C++ talk: https://youtu.be/rX0ItVEVjHc

3 Likes

apparently I wrote Building Git to explain a complex problem to rust devs who could then help me build it in rust

1 Like

&mut obj as *mut *mut c_void :metal:
i just hear scandinavian death metal reading that

Nick Gideo via Rust VST chat

2 Likes

it’s true that the more i look at other people’s unsafe code the more i relax at people questioning how much i use unsafe code

@Lokathor on the community discord

4 Likes

What does it mean to be an expert in Rust?

Understands lifetimes

u/aesamattki on reddit.

Lol, my initial reaction was “It does. That’s why it outlives all the other lifetimes” :joy:

3 Likes