Lukas Wirth

Excited to announce that I'll be working on @zed.dev starting today!

Woah congrats!

New blog post: I am a Rust compiler engineer looking for a new job

nnethercote.github.io/2025/07/18/l...

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.

It seems like we can mostly ignore those new bounds and thing should just work™ again but we'll see

Rust 1.89 contains the sized hierarchy changes which turns out completely break rust-analyzer's type inference 😩

Our metrics dipped quite badly when beta was bumped yesterday rust-analyzer.github.io/metrics/?sta...

Sized hierarchy OR: github.com/rust-lang/ru...

> However, are there problems with a proc-macro returning more than one item?

That is also just fine, derives are not even required to output a trait impl. It's just convention as that was what they initially were meant for. Nowadays its more just a macro kind that cannot change its input.

Note that `const _` is exemtp from the non-local lint, as its currently the only way to generate code without polluting the surrounding scope due to the lack of stable declaration site hygiene. So the first one is be preferred if you don't want to leak generated code out of its scope.

hey, lukas and i gave a talk about salsa in rust-analyzer and i think it’s a good time; check it out

A photo of the book building a debugger

Whew this is bigger than expected

Is there a cargo plugin that goes through your codebase and lints on any visibility qualifier that could be shrinked in scope? 🤔

That is if there is some definition `pub(crate) thing` but that is only ever used in the module itself I want something that tells me, "This `pub(crate)` can be omitted"

if it takes a long time to do, can you really call it "prompt" engineering

Discovered riichi mahjong yesterday and I absolutely love it, super interesting game (while also being super frustrating due to its luck component)

Only took me one and a half years of bouldering to get my first finger injury let's go. Fortunately in a way that I can still use my finger, just gotta take a break from bouldering it seems :(

Currently doing a rebase with a ton of conflicts in it and I am once again tempted to change the import granularity in rust-analyzer to per item (that is one item per import per line).

Doesn't help that this rebase is across an edition bump which apparently changed rustfmt formatting for imports...

Finally fixed rust-analyzer not carrying over `#[cfg(..)]` attributes when inserting imports into the file github.com/rust-lang/ru...

Trigger VSCode to rename after extract variable assist is applied · rust-lang/rust-analyzer@8efe8a8 When the user applies the "Extract Variable" assist, the cursor is positioned at the newly inserted variable. This commit adds a command to the assist that triggers the rename action in V...

rust-analyzer emulates this for the `extract to variable` assist by making the edit and then triggering the client to trigger a rename request. This does unfortunately need client side glue, so its not quite what you are after (do let me know if you figure something out :) github.com/rust-lang/ru...

The string literals span is being re-used for things, so we just show all the things with the strings span on hover which can be non-string tokens in the expansion. We merely have a heuristic that tries to sort these results according to what you hovered initially which doesn't do anything here

A screenshot of a VSCode hoverbox from hovering the string literal in `#[serde(skip_serializing_if = "Option::is_none")]`

why does this still work lol. I guess I didn't remove it, I just changed our heuristics to no longer special case string literals.

wait what, we still do that? I thought for sure I removed that lol

Fyi, `simplify-parents` usually removes most (if not all) merge commits (if you haven't used that). Really nice to turn a PR history linear jj-vcs.github.io/jj/latest/cl...

Selecting all tiles was in fact not correct

A tile clicking image base captcha with 4x4 tiles. The entire image is one giant bus and the captcha asks to select all tiles with buses.

I just got an amazing captcha

Github honestly is the worst tool to review PRs with, I hate it so much especially for bigger diffs

Yeeee don't do that

Screenshot showing the pull request tab of rust-lang/rust-analyzer with 30 open PRs

I've been neglecting reviews on rust-analyzer for too long again it seems 😩

Is this guy one?

So apparently I developed insomnia last night, perfect timing given there is 5 day weekend here now ugh

Gotta make sure this succeeds :^) (syn / serde is ruining compile times in r-a)

Looking at what jj seems to be using for its log command github.com/jj-vcs/jj/bl..., its crates.io/crates/sapli...

Maybe that's usable for you?