starting work next week… hopefully i remember how to program
trying to make sense of ocaml modules and their conceptual relationship to rust traits... rust essentially enables "module inference" which i think is neat, especially thinking about what constraints this requires compared to ocaml where modules need to be named directly in functors
I wrote about this sort of corporate mis-allocation of maintainer roles a while back and it's tragic to see such a vivid example. Let maintainers be maintainers! graydon2.dreamwidth.org/306832.html
Michael (compiler-errors) Goulet@errs.io · 11mo agoI 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.
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.
coding interviews are a joke and i'm gonna be so pissed if i can't get a job because i don't know how to find some "trick" to solve some toy problem that has nothing to do with developing and maintaining a massively complex compiler codebase, which is a thing that i *am* actually good at doing.
github.com/rust-lang/ru... 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/ru... If you've ever hit any of these issues, I'd like your feedback when that PR lands.
Consider WF of coroutine witness when proving outlives assumptions by compiler-errors · Pull Request #143545 · rust-lang/rust
TL;DR This PR introduces an unstable flag -Zhigher-ranked-assumptions which tests out a new algorithm for dealing with some of the higher-ranked outlives problems that come from auto trait bounds o...
github.com
Howdy all. I'm unfortunately not going to be with my employer for much longer due to team relocation. If anyone has any info on roles that would allow me to continue my Rust compiler work (in New York City), they'd be greatly appreciated.
On my way back home after RustWeek 2025. So, so proud that we hosted the Rust Project All-Hands, the 10 years of Rust celebration, and the biggest Rust conference yet. See you all next year! Thanks to my co-organizers Jana, Laura, @tertsdiepraam.bsky.social and @mara.bsky.social ❤️ #rustlang #rust
Live from the 10 Years of Rust celebration in Utrecht, Netherlands, we are very happy to announce a new version of Rust, 1.87.0! See the blog post and release notes for all the details! blog.rust-lang.org/2025/05/15/R...
I feel like the work i did to improve diagnostics in github.com/rust-lang/ru... is paying off a lot now. I see it all the time. We now report "purely additive" typo fixes for things like methods using an inline syntax that highlights what to *add*, rather than the whole identifier.
![A method resolution error:
```
error[E0599]: no method named `try_structurally_resolve` found for reference `&fn_ctxt::FnCtxt<'a, 'tcx>` in the current scope
--> compiler/rustc_hir_typeck/src/pat.rs:694:31
|
694 | *self.try_structurally_resolve(pat.span, peeled_ty).kind()
| ^^^^^^^^^^^^^^^^^^^^^^^^
|
help: there is a method `try_structurally_resolve_type` with a similar name
|
694 | *self.try_structurally_resolve_type(pat.span, peeled_ty).kind()
| +++++
```](https://cdn.bsky.app/img/feed_thumbnail/plain/did:plc:iepdzjv2sqzadasza66rrktz/bafkreigkahe46wz7mnkosjfovylrponnk3vr6byapliud2o2lxpq23ygzi)
A new subway diagram has arrived! MTA leadership (including MTA Chair and CEO Janno Lieber and Chief Customer Officer Shanifah Rieara) unveiled a reimagined subway map, its first new design in half a century. Check out the new map on digital screens in stations, and as it rolls out on train cars 🚇
** Speaker announcement ** Catch this talk at RustWeek 2025! Speaker: Michael "compiler-errors" Goulet / @errs.io Title: (Almost) Everything You Should Know About The Compiler Frontend Info & tickets: rustweek.org/talks/errs/ See you in Utrecht 13-17 May, 2025! #rustweek #rustlang
(Almost) Everything You Should Know About The Compiler Frontend - RustWeek 2025
RustWeek 2025, The Netherlands - May 13 - 17 2025
rustweek.org
soooo this. I started into the abyss so much, I can only see the abyss now
gabby@fullmoon.id · last yr.Programming language author: I have made a huge mistake and people have to constantly work around my mistake in perpetuity Programming language user: I love everything about this language and these workarounds feel so sensible, idiomatic, and pragmatic to me
I contributed quite a few things to this release, including async closures and lots of parts of Edition 2024. I'm glad that it's finally out 💖🦀
Mara Bos@mara.bsky.social · last yr.🦀 Rust 1.85.0 has been released! ✨ One of the bigger #rustlang releases in a while, as it contains *async closures* and *the new Rust Edition*: Rust 2024! 🎉 blog.rust-lang.org/2025/02/20/R...
No I don't want AI generated PRs on my repository thank you very much
i should stop working on public-facing features. i'm going to lock myself in a monastery and only refactor decrepit deeply-internal compiler apis that nobody can have opinions.
lots of existential dread recently i'd like to work on rust in peace pls :>
Async closures went from (practically) unimplemented to stabilized (on nightly) in approximately a year. Hopefully they'll land fully stable in 1.85, and I hope they help solve some of your async problems. github.com/rust-lang/ru...
Stabilize async closures (RFC 3668) by compiler-errors · Pull Request #132706 · rust-lang/rust
Async Closures Stabilization Report This report proposes the stabilization of #![feature(async_closure)] (RFC 3668). This is a long-awaited feature that increases the expressiveness of the Rust lan...
github.com
Wow! The new trait solver now fully builds the Rust compiler. Huge milestone. Now comes the long tail of getting all the *other* crates in the world to compile too :) github.com/rust-lang/ru...
[DO NOT MERGE] bootstrap with `-Znext-solver=globally` by lcnr · Pull Request #133502 · rust-lang/rust
A revival of #124812. Current status: ./x.py b --stage 2 passes 🎉 commits support revealing defined opaque post borrowck #133501 do not constrain infer vars in find_best_leaf_obligation #133493 94...
github.com