Profile avatar
lukaswirth.bsky.social
rust-analyzer team lead ferrocene spec writer engineer at @ferroussystems.bsky.social
33 posts 199 followers 117 following
Regular Contributor
Active Commenter

Sometimes I'd like it if Rust would allow you to make a struct constructor unsafe instead of having to wrap it in a module to make it private while exposing an unsafe constructor function and re-exporting the type. That alternative adds a lot of noise.

Had some fun with prototyping a very cursed idea in rust-analyzer today.

I just realized that you can `catch_unwind` assertions in Rust and I am unsure how to feel about that

the (||{})()s will continue until try_blocks lands, i guess

Figured I'd give lowering const generic parameters another try in rust-analyzer: github.com/rust-lang/ru... Turns out that was a mistake, I have now come to the realization that I'll have to rewrite pretty much all of our definition IRs (an absolutely massive refactor of an unknown size to me)

I should really get to turning my EuroRust talk into a blog post so I can point people to that (instead of a video) for tips on how to make proc-macros work better for rust-analyzer ...

"By forcing me to get object ownership in order and separate concerns, the borrow checker prevented a logic bug." #rustlang mental-reverb.com/blog.php?id=46

I do have to say 300 characters per post is quite a low limit.

This year is gonna pretty substantial for rust-analyzer I believe. We (and with that I mainly mean @davidbarsky.com) are closing in on migrating to the new iteration of github.com/salsa-rs/sal... which will hopefully allow us to improve performance, memory usage and implement a couple of wanted

this post is gunning for the ana mardoll “it’s ableist to ask writers to read” throne

rust-analyzer now has some basic* parameter variance inferrence and it shows it on hover! *basic as in it can't handle cyclic dependencies yet for temporary implementation reasons, it also struggles with usages within const arguments.

Another day goes by where I wish we had disjointness based on associated types github.com/rust-lang/rf...

I once again demand `std::ops::Not` to be part of the prelude, postfix `.not()` is superior to prefix `!`

Macros are notoriously hard to decipher for IDE’s. How does Rust Analyzer handle them? 🤔 @veykril.bsky.social from Ferrous Systems shares insights on how `rust-analyzer` enables features like completions and search, despite macro challenges. ➡️ https://buff.ly/4fLhIlH #eurorust24 #rustlang

In half a week I get to look at the results of what 4 weeks of ignoring rust-analyzer looks like! Excited to see my notification backlog.

Cool my flight home for tomorrow might be canceled (Finnair is giving mixed signals)

The Shinkasen is a pretty cool experience I have to say (especially when you are used to the Deutsche Bahn)