Skip to main content

mastodon - Link to source

"Many people complain that the #Rust borrow checker is hard to wrap your head around. Having done a PhD in compiler design and being very familiar with dataflow analysis, there weren’t any major surprises for me. Still (...) I needed to learn the rules of the system as to how and where you’re allowed to borrow, (...)."

My ass has been laughed off and has not been seen since shopify.engineering/porting-yj…


Our Experience Porting the YJIT Ruby Compiler to Rust

In this post, I want to give a nuanced perspective on our experience porting YJIT from C to Rust. I'll talk about the positives, but also discuss the things that we found challenging or suboptimal in our experience.
Shopify
#rust
in reply to fasterthanlime 🌌

fasterthanlime 🌌
mastodon - Link to source
fasterthanlime 🌌
• •
That said, I think YJIT being ported to Rust is really cool! And I like the article overall, I just had a good hearty laugh, I don't mean to put it down.
in reply to fasterthanlime 🌌

obw
mastodon - Link to source
obw
• •
definitely seems like a lot of the papercuts in the article are due to the "no dependencies except stdlib" restriction (which might've been unnecessarily inherited from C?) but at the same time, I find myself agreeing with some of the criticisms of e.g. CStrings and number casting.
in reply to obw

obw
mastodon - Link to source
obw
• •
like, yeah, I would like better CString ergonomics in stdlib, and I often wonder how much i'm shooting myself in the foot when I write `x as u16` and clippy doesn't issue a warning or anything
in reply to obw

Federico Mena Quintero
mastodon - Link to source
Federico Mena Quintero
• •
If you haven't seen it, the 'cast' crate is pretty useful for this.
⇧