rust-analyzer is experimenting with a really clever feature: allow types to open a link to their external docs! https://github.com/rust-analyzer/rust-analyzer/blob/master/docs/dev/lsp-extensions.md#open-external-documentation
I've definitely thought about referencing external resources from an editor: in principle you could even fetch the first paragraph inline too!
miniblog.
Related Posts
The author of rust-analyzer discussing how language features help or hinder fast IDEs.
If you allow `from m import *` you can't analyse files in isolation, and it's even harder in Rust.
Structs are great in Rust, but sometimes I find them a bit heavyweight. There's a little more syntax than e.g. OCaml, for type definitions and usages.
I end up using more structs (records) in OCaml as a result.
rust-analyzer has "convert tuple to named struct", which helps.
I enjoyed this interview with Lukas Wirth, one of the maintainers of rust-analyzer: https://rustacean-station.org/episode/lukas-wirth/
I didn't realise how little code was shared between rustc and rust-analyzer (only lexing and type layouts). This makes it hard to track new Rust features.