Replying to @timothyac__
nope, I was already in the office in NYC
I urge companies to take funding contributors seriously, in ways that aren’t tied to projects and goals. Being a generalist in the compiler meant that often I wasn’t working towards a roadmap, but my contributions *always* paid off in the long term extensibility of the language.
That does mean I’ll be scaling back my Rust contributions over the next few months before I start my new job. Sorry to the folks who were looking forward to stuff I had in the pipeline. I really would’ve liked to deliver async fn in dyn traits or `-Zhigher-ranked-assumptions`.
Unfortunately, it was not possible to snag a new job working on Rust in the way that I do today (type system/compiler frontend) especially with the freedom I have today, and I couldn't possibly be jobless for an indeterminate amount of time waiting for the right role to show up.
I’m glad I got the opportunity to do amazing work on Rust over the last 3 years. It’s hard to quantify, but I hope people saw a difference due to my work on async traits/closures, the type system, diagnostics, style team, ICE fixes, internal refactors, speedups, edition 2024 etc.
Today’s my last day at AWS working on the Rust compiler. Unfortunately, back in July I received notice that I had to choose between moving to Boston from NYC, or leaving the company due to RTO policy. I unfortunately couldn’t abandon the city I plan on being my long term home.
The PR is pretty technical, so I don't expect that many people to understand what's going on in it, but hopefully when it lands I can ask people to test their code with `-Zhigher-ranked-assumptions` and see if it fixes their code ✨
github.com/rust-lang/rust/pu… is the beginning of a fix for all the nonsense lifetime errors you probably encounter when writing async code in Rust that heavily uses lifetimes.
github.com/rust-lang/rust/is…: if you've ever hit any of these issues, I'd like your feedback when the PR lands.
I know I've tweeted about asking for leads before, but this time it's serious. DMs should be open, and apologies for possibly ignoring previous reachouts :)
Bad news -- I'm not going to be with my employer for much longer due to team relocation demands. If anyone has any leads for roles that would allow me to continue my Rust compiler work (in New York City), they'd be greatly appreciated.
- async closures
- impl trait capture rules + precise capturing
- implemented `'r#` raw lifetime syntax
- fixed major bugs with temporary scope change detection
- improved error for never fallback changes
- improved the impl of expr_2024 macro fragment
- reviewed unsafe blocks
I contributed quite a few things to this release, including async closures and lots of parts of Edition 2024. I'm finally glad that it's out.
Canada
CanadaConnected via WebAccount-level information, not a live location or per-post device.
Rust 1.85.0 has been released! 🌈🦀✨
Not only does this release add async closures, it also includes a whole new Rust Edition, Rust 2024! 🎆🚀
Check out the blog post for an overview of all the changes and additions: blog.rust-lang.org/2025/02/2…
Replying to @zack_overflow
i’m productive enough just print debugging, but also i’m lucky to only need to debug a program that has short repeatable runs
:)
The #rust community is crazyyyyyy! Or at least @compiler_errors is.
- I created an ICE report.
- less than an hour later, Ben Kimock arrived and completed it with a minimal repro.
- two minutes later, @compiler_errors assigned himself and fixed it within half an hour.
👏👏👏