rustfmt VS rust-analyzer

The new style still supports single line let-else, and there is a configuration parameter to make it be on one line also for longer lines.

Yacin Tmimi for actually implementing the bloody thing

I’m not sure they are? I don’t mean this to criticize anybody on the project — I’m sure they have other things going on — but there are a whole bunch of open PRs without even a single comment.

It seems there is an issue about this dating all the way back from 2018 but yet it still hasn't been fixed.

Presumably, https://github.com/rust-lang/rustfmt/pull/5690

However since 4179 recent versions should merge configuration files. Not sure what the details / specifics are but if just ignoring the file entirely is not good enough you might give it its own directory and rustfmt.toml file and see if that works.

Rustfmt is a tool that formats Rust code in compliance with style guidelines. Its name precisely reflects its purpose. To install rustfmt, you can run rustup component add rustfmt. Once installed, you can execute cargo fmt to format Rust code in your workspace. If you require further information, you can visit rustfmt’s GitHub repository.

code must be formatted with rustfmt.

Yes, some cases are not yet supported (https://github.com/rust-lang/rustfmt/issues/4914).

Just FYI, the let-else suggestions will only work until rustfmt settles on a format for it. So you may be surprised when this happens and it suddenly changes.

Agree this is not a problem. rust-analyzer also includes a boatload of custom extensions. Here's how "query type of selected expression" works, for example:

https://github.com/rust-lang/rust-analyzer/blob/master/docs/...

For example: https://github.com/rust-lang/rust-analyzer/blob/master/docs/...

> If you create an LSP, it will work best in VS Code.

Any editor can work just as well as (or even better than) VS Code.

I am not a Rust dev. It surely looks great.

However, from what I understand it seems to supply just a parser separate from the Rust compiler (https://github.com/rust-lang/rust-analyzer/tree/master/crate...) trying to keep up with Rust‘s development. So, in principle, it could have been just another treesitter parser plugin, too.

So, again, the LSP framework does not directly provide any magical benefit over a static parsing framework. All the semantic analysis capabilities stem from a good parser.

You may file issue at github rust-analyzer

I've contributed to rust-analyzer and nushell and had a great experience in both! Tons of open issues with a huge range of difficulties, and the maintainers are really helpful in providing hints to get started.

For something more concrete you can try and ask around on their zulip or browse their issues.

More info here: https://rust-analyzer.github.io/ and here: https://rust-analyzer.github.io/manual.html#installation

You can submit feature requests in the repository: https://github.com/rust-lang/rust-analyzer/

sh git clone https://github.com/rust-lang/rust-analyzer.git && cd rust-analyzer cargo xtask install --server

Thanks for the ideas! Separating out presentation crate into it's own crate sounds like a great idea. Re "temporarily stopping rust-analyzer", I came across this trick[0] to make RA use a different build path (trading off disk-space for speed, but I mean, disk space is cheap).

Re: cranelift, I gotta check that out! Thanks for the reminder!

[0] https://github.com/rust-lang/rust-analyzer/issues/6007#issue...