Six months into Rust after years of garbage collected languages. My programs work and my strategy for the borrow checker is, honestly, to clone things until the errors stop. I know this is the thing everyone says not to…
Nightly job that reads about 9GB of gzipped CSV, parses it, dedupes on a composite key, and writes Parquet. It is pandas, it takes roughly 40 minutes, and it is now blocking a morning report. I have one week I can spend…
Twelve async workers fetching pages, all consulting a map of about 50k domain to rate limit entries. Reads are maybe 95% of accesses, writes happen when a new domain appears or a limit updates. I can either wrap it in…
I have a and I'm iterating over incoming items, and for each one I want to look at the last element already in the vec to decide whether to merge or push a new one. The compiler tells me I can't borrow as mutable…
Internal service, about 30 endpoints, Postgres behind it, moderate traffic where p99 matters a little but nowhere near microsecond territory. Both of us are Python people, one of us has written a couple of small Go…
I have a trait with an async method, implemented for a struct that holds an . It compiles fine and the tests pass when I await it directly. The moment I call it inside I get a wall of text ending in 'future is not…
I have read the official book once end to end and I can write code that compiles, but I am pattern matching on error messages rather than understanding what I am doing. Cloning things until the compiler stops…
I have a struct holding a and I want a method that returns an iterator over the records matching a predicate, without collecting into a new Vec. Every attempt ends in either a lifetime error about the closure, or the…
Six weeks in, coming from ten years of Python and some C. I can write code that works but I spend maybe half my time restructuring things to make the compiler happy, and I never predict in advance which design will be…