Tagged “rust”

Blinking An LED On An STM32 With Embedded Rust

How The 2018 Edition Quietly Fixed My Rust

Parsing Without the Regret, Using nom

Trait Objects vs Generics, With Numbers

Fighting the Borrow Checker, and Losing Gracefully

Losing Gracefully To The Borrow Checker

How We Did Rust Error Handling Before anyhow Saved Us All

I Benchmarked Trait Objects Against Generics So You Don't Have To

The Edition That Quietly Reshaped How I Write Rust

I Rewrote a Shell Script in Rust, and I'd Do It Again

rewriting a shell script in rust, and counting the cost

the borrow checker was right and i was tired

losing to the borrow checker, then thanking it

two years of rust in production, and an honest tally

how we did rust error handling before anyhow turned up

async/await landed and i rewrote everything

i rewrote a 40-line bash script in rust, here's the honest tally

parsing a config format with nom

blinking an LED the hard way, in Rust

the borrow checker was right and i was wrong, again

parsing a config format with nom, one combinator at a time

how i learned to lose to the borrow checker gracefully

trait objects vs generics, with actual numbers

the 2018 edition changed how i write rust

the async rewrite i swore i wouldn't do

i rewrote a 40-line shell script in rust and i'd do it again

the rust i write now started with the 2018 edition

how we handled rust errors before anyhow saved us

what two years of rust in production actually taught me

dyn or not: i finally benchmarked it

i rewrote a thirty-line shell script in rust

two years of rust in production, the honest ledger

a little cli in rust, and whether the borrow checker earned its keep

the borrow checker was right and i was the bug

two years of rust in production, the honest ledger

the great async rewrite, and what it actually cost me

i benchmarked dyn vs generics so you can stop arguing about it

parsing a config format with nom, and learning to think in combinators

dynamic dispatch isn't as slow as you've been told

how rust 2018 quietly rewired my instincts

parser combinators finally clicked, thanks to nom

trait objects vs generics, a real benchmark

nom finally made parsing feel less like a chore

how we did rust errors before anyhow and thiserror turned up

what rust error handling felt like before anyhow turned up

blinking an led on an stm32 the hard, satisfying way

what rust error handling felt like before anyhow turned up

i rewrote a service in async rust and learned what coloured functions cost

nll, no extern crate, and how rust started feeling easy

rust in production, two years of regrets and wins

when every crate brought its own error type

i benchmarked dyn vs generics so you don't have to

async/await finally clicked, so I rewrote everything

i rewrote a futures-combinator mess into async/await and regret nothing

i benchmarked dyn versus generics so i could stop guessing

i wrote a small cli in rust and i'm still arguing with myself about it

rewriting it all for async/await

how the 2018 edition quietly retrained my hands

nom made me stop hand-rolling parsers, mostly

async/await in rust, and the rewrite i couldn't resist

parsing a config format with nom, and liking it

rewrote a ten-line shell script in rust, regret nothing

blinking an led on an stm32 in rust, and being surprised it worked

i lost an argument with the borrow checker, and it was right

losing to the borrow checker, gracefully

i rewrote a tiny shell script in rust and i regret nothing

one more note on the async port: select! is sharper than you think

async/await is stable, and i went and rewrote the lot

dyn or generic? i finally measured instead of guessing

a year with async/await, and the rewrite I do not regret

the borrow checker was right and i was wrong, again

fighting the borrow checker and losing gracefully

error handling before anyhow existed

async/await finally clicked, so naturally i rewrote the lot

rust errors back when you wrote every From by hand

blinking an led the hard way, in rust

error handling before anyhow existed

i rewrote a shell script in rust and i'm not sorry

what the 2018 edition quietly fixed

the borrow checker was right and i was tired

async/await is nearly here and i couldn't wait

the 2018 edition quietly rewired my rust habits

parsing without regret, using nom

what rust error handling felt like before the crates showed up

the borrow checker was right and i was tired

the error said "no such file" and not which one

the error type i wrote forty times before i learned the trick

i rewrote a 40-line shell script in rust and i'd do it again

what rust error handling felt like before anyhow turned up

i rewrote a thirty-line shell script in rust, and mostly enjoyed it

rust feels different since the edition landed

parsing a config format with nom, and learning to think in combinators

the borrow checker was right and i was being stupid

the small joys of the 2018 edition

the borrow checker was right and i was wrong, again

i wrote a 200-line tool in rust to avoid a 20-line shell script

parsing a daft little config format with nom

i rewrote a 40-line shell script in rust, and i'd do it again

i rewrote a shell script in rust and i have feelings

i rewrote a tiny shell script in rust, here's the honest accounting

the borrow checker was right and i was wrong, again

parsing a config format with nom, and learning to think in combinators

parsing a log line with nom, and why i stopped reaching for regex

the borrow checker was right and i was wrong, again

fighting the borrow checker and losing gracefully

a small parser, written with nom

parsing a log format with nom, and learning to think in combinators

the borrow checker was right and i was wrong, again

the .context() helper i keep copying between rust projects

losing to the borrow checker, then realising it was right

a christmas-break rust cli, and the honest cost of it

error handling in rust, the year before anyhow saved us all

another small rust cli, and the part i keep getting wrong

when rust error handling meant rolling your own

a rust tool to find duplicate files, and whether it earned the build time

i tried to mutate a vec while iterating it, and rust said no

the borrow checker was right and i was holding a reference too long

the borrow checker was right and i was tired

the day the borrow checker was right and i was wrong

a weekend rust cli, and whether the borrow checker earned its keep

the one-liner that talked me out of rust

another small tool, another afternoon in rust

the borrow checker was right and i was tired

another small rust cli, and the parts i'd do differently

rolling your own error type in rust, the long way round

the borrow checker was right and i was wrong

the borrow checker won, and i'm fine with it

the borrow checker was right and i was wrong

a tiny cli in rust, and whether it earned its keep

a little cli in rust, was it worth it

i rewrote a shell script in rust and i'm not sorry