Twitter | Search | |
rust-analyzer
Experimental language server for the Rust programming language. Support at
24
Tweets
3
Following
380
Followers
Tweets
rust-analyzer Jan 29
Replying to @TedMielczarek
Somewhat: our intention is to upstream all the work to rustc and eventually merge it with rust-analyzer. It's just the scale of changes is so big that starting from scratch was easier :-) One can say that rust-analyzer to rustc is what Servo is to Firefox.
Reply Retweet Like
rust-analyzer Jan 29
Replying to @TedMielczarek
Only a short paragraph in readme right now: Adding some actual docs to the website is on the todo!() list...
Reply Retweet Like
rust-analyzer Jan 29
Hey, we've tracked down a recent-ish (couple of releases back) performance regression when using `cargo check`. Today's extra release contains a fix: The problem was that we accidentally were running long computations on the main loop.
Reply Retweet Like
rust-analyzer Jan 27
Replying to @rust_analyzer
The auto-import feature builds on infrastructure that many people helped to put in place the last year, but the final push was done by !
Reply Retweet Like
rust-analyzer Jan 27
Reply Retweet Like
rust-analyzer Jan 22
Replying to @softprops @solomatovk
Slightly longer than a tweet answer:
Reply Retweet Like
rust-analyzer Jan 21
Replying to @solomatovk
I hope to get to publishing VS Code extension and auto-downloading of the server soon. However, by itself this won't solve stability problems :-) rust-analyzer is still an alpha-quality software: a lot more effort is needed before it works 100% reliably.
Reply Retweet Like
rust-analyzer Jan 21
Little known feature of rust-analyzer: in symbol search, you can use # to search for functions and fields (the default is type) and use * to search across dependencies. Would love to see first class support for this in LSP!
Reply Retweet Like
rust-analyzer Jan 20
Changelog #8 We also have a new logo by !
Reply Retweet Like
rust-analyzer Jan 15
Replying to @rust_analyzer
This feature was implemented by in .
Reply Retweet Like
rust-analyzer Jan 15
Instead of adding a bool parameter to a function, consider providing two functions, do_foo and do_bar. Even if you don't do this, rust-analyzer will try to make call-site more readable :-)
Reply Retweet Like
rust-analyzer Jan 13
Changelog #7 Loots of good stuff this week, including binary release:
Reply Retweet Like
rust-analyzer Jan 8
Tip: with rust-analyzer, you can go to definition, or to the *type* of the definition!
Reply Retweet Like
rust-analyzer Jan 6
Replying to @hoodie_de
Genetic programming: I copy-paste the previous one and mutate it appropriately.
Reply Retweet Like
rust-analyzer Jan 6
Reply Retweet Like
rust-analyzer Dec 30
Changelog #5: Support for `cargo watch` is moved to server side, and works with all editors!
Reply Retweet Like
rust-analyzer Dec 24
Replying to @zmanian
Items nested into functions (as opposed to items nested directly into modules).
Reply Retweet Like
rust-analyzer Dec 23
Changelog #4: Preliminary support for local items has landed!
Reply Retweet Like
rust-analyzer Dec 16
Reply Retweet Like
rust-analyzer Dec 13
Replying to @hoodie_de
The default is still #747474: it's impossible to pick the right default, as everybody has a different theme
Reply Retweet Like