Skip to content
Hallway
0:00 / 0:00

#orphanrules#coherence#pathfinder

Bay Area Rust March 2017: GPU Rasterization, the Orphan Rules, and Rocket

Rust Programming Language

70K subscribers • 72 videos on Hallway • Conference channel

YouTube
  • Recommended by 4 people: 4 in engineering communities.

Advanced. Deep dive for people who know the field.

6.3K views7 years ago4 recommendations

Programming languagesSystems programmingRustCompilers and interpretersRendering

This meetup features talks on Pathfinder GPU font rasterization, Rust's coherence and orphan rules, and the Rocket web framework.

meetup.com/Rust-Bay-Area/events/237709786/ • Patrick Walton: Pathfinder ( pcwalton.github.io/2017/02/14/pathfinder), a fast GPU-based font rasterizer for Rust () • Without Boats: Coherence and the orphan rules () • Sergio Benitez: Rocket (rocket.rs/), a plugin-powered web framework in Rust focused on ease of use, expressibility, and speed ()

Why it's here

4 people recommend this

What people say. Highly recommended by the community as one of the best explanations of Rust's coherence and orphan rules.

Moments people linked to

u/Saefrochin r/rust • Recommends

On “A Home for Orphan Instances”

Don't Rust's orphan rules forbid the entire scenario that this blog post is dedicated to fixing? Withoutboats gave a talk on this a little while ago that was only recently uploaded. I disagree that this blog post is relevant to Rust.
6View on Reddit

u/sunjayvin r/rust • Recommends

On “What are the technical reasons for the orphan rule?”

There's a great talk by withoutboats that explains this in detail. It starts about 40 minutes into this video: link to this video
3View on Reddit

u/sellibitzerustin r/rust • Recommends

On “Hey Rustaceans! Got an easy question? Ask here (25/2019)!”

You ran into an issue where the compiler applied some rules to reject your `impl` in order to retain "coherence". Essentially, what you're trying to do won't work. You have to find a different approach. As for the rules about when and when not a trait impl is allowed, I'm fuzzy on the details. But I've seen this talk by WithoutBoats being recommended to shed some more light onto coherence rules (including *why* we have these rules).
3View on Reddit

u/0x7CFEin r/rust • Recommends

On “What's your favorite Rust conference talk?”

One of the best (if not *the* best) talks about Rust I've ever seen. Definitely worth its time if you want to know what really is Rust about. By the way, Jason Orendorff is the second author of "Programming Rust" book. Another video I strongly suggest to watch is Boats' recent talk on the coherence, although it's quite advanced topic for a newbie. But still it's a very good explanation of what the heck coherence is and why it's there in the first place. I was surprised to know that even seasoned rustaceans often don't know about it.
2View on Reddit

u/bocckokain r/rust • Mentions

On “Introducing Rust to talented teens”

I would start on a more generic note, outline the problems that Rust solves from a broader perspective first. We have data, we want to be fast so we want to avoid copying - we need references. What can go wrong with references? What is required to avoid data races (define data race, synchronization or enforcing (n read only ref XOR 1 mutable ref))? Some examples, verbal, C++. How GC languages solve this (what GC does), what's wrong with that, when it's okay, when it should be avoided? What can be the alternative? You need to track lifetimes. Some explanation, desugared simple cases, perhaps return to an earlier C++ example in Rust and show the error you get, mention how hard would that be t…
1View on Reddit