Create accountLogin

Recent searches

No recent searches

Search options

Only available when logged in.
veganism.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
Veganism Social is a welcoming space on the internet for vegans to connect and engage with the broader decentralized social media community.

Administered by:

Server stats:

292
active users

veganism.social: AboutStatusPrivacy policy

Mastodon: AboutGet the appKeyboard shortcutsView source codev4.3.0-alpha.5+vegan

#rustlang

118 posts94 participants8 posts today
Public
Chris Woody Woodruff

Day 11 of learning Rust as a C# dev:
The borrow checker isn’t your enemy. It’s your tough-love mentor.
It yells a lot, but it’s making you a better developer, whether you like it or not.

Read more:
woodruff.dev/the-borrow-checke

Chris Woody Woodruff · The Borrow Checker: Rust’s Tough-Love Mentor - Chris Woody WoodruffYou think you’ve been writing safe code… until you meet the Rust borrow checker. Then suddenly, your once-proud instincts are being side-eyed by a compiler that’s not mad, just disappointed. Today, on Day 11 of my Rust journey, we talk about the infamous, unyielding, sometimes infuriating, but ultimately brilliant guardian of Rust safety: the borrow checker.
#RustLang#CSharp#DotNet
Public
Chris Woody Woodruff

Day 10 of learning Rust as a C# dev:
Borrowing in Rust feels like ref, but stricter, smarter, and way more protective.
It’s not just syntax. It’s a whole new way of thinking about data.

Here’s how it works:
woodruff.dev/borrowing-and-ref

Chris Woody Woodruff · Borrowing and References: Rust’s Version of ref (But Nicer) - Chris Woody WoodruffIf you've been writing C# for a while, you’ve likely crossed paths with ref, in, and out parameters. They allow you to pass variables by reference, enabling a method to read or modify the original value. Useful? Definitely. Safe? Uh... sometimes. In Rust, there's a similar concept called borrowing. It uses & and &mut, and it feels a lot like passing ref or in in C#, but with one significant difference: The compiler enforces safety rules that make data races and invalid access impossible. Today, we’re diving into borrowing, references, and how Rust holds your hand (and your memory) without letting you write foot-gun code.
#RustLang#CSharp#DotNet
Public
Jacob Pratt

In #VSCode, the code lenses now include an outline around parts of it (such as "🅁un 🅃ests"). I'm not sure if this is from #Rust analyzer or VS Code itself, as I updated everything last night.

Is there a way to get rid of this outline (likely a border in the CSS)? It is distracting to the point that I'm considering turning off code lenses if it can't be disabled.

#RustLang#programming
Public
Chris Woody Woodruff

Day 9 of learning Rust as a C# dev:
I moved a variable, and the compiler yelled at me.
It turns out that Move Semantics isn't just a feature... it's a mindset shift.

Here’s what I learned:
woodruff.dev/move-semantics-in

Chris Woody Woodruff · Move Semantics in Rust: What Just Happened to My Variable? - Chris Woody WoodruffOkay, so picture this: you're cruising along in your nice, type-safe Rust code, and suddenly... your variable vanishes. Not literally, of course. But the compiler throws a fit, and you’re left staring at an error that says something like: "value borrowed here after move". Wait, move? Welcome to move semantics, Rust’s very opinionated way of managing memory and keeping you from accidentally using things that don’t belong to you anymore. Today’s post is a follow-up to yesterday’s crash course in ownership and this one might sting a little at first if you're coming from the comfy world of .NET’s reference types. But stick with me. It’s about to make sense.
#RustLang#CSharp#DotNet
VegansExploreLive feeds
About