gitoxide VS rust-analyzer

But I'd suggest joining an existing project instead. This week in Rust has a call for participation section each week. There are also some exciting rewrites like arti, gitoxide, fish, and a steady stream of projects announced in this sub.

There's a re-implementation of git called gitoxide

Gitoxide is useful in other Rust programs that need git integration, e.g. Cargo[1] or Helix[2].

[1]: https://github.com/Byron/gitoxide/issues/106

I don't know how far he intends to take it, but the author of gitoxide (which is just a library, like libgit2) uses it to power a git CLI called gix. As of October it looks like it can do fetches and clones: https://github.com/Byron/gitoxide/discussions/623 .

Since the git CLI is subcommand-based, it wouldn't be too hard to provide replacements for individual git subcommands one at a time.

It'll be interesting to see where the gitoxide[1] project goes, being a rust implementation of git

[1] https://github.com/Byron/gitoxide/

gitoxide, because, well, everything around rust is kind-of low-hanging fruit of puns to make

After having used the gitoxide lib in bacon last week so that ignored files don't trigger jobs on change, I'll try to see whether I can replace git2 with gitoxide in a few other applications. Gitoxide lib is still a little rough in parts but I really like when I can replace a native lib with a pure Rust one.

go build 3.62s user 0.76s system 171% cpu 2.545 total

I was looking forward to parallel front-end[4], but I have not seen any improvement for these small changes.

[1]: https://github.com/rust-lang/rust-analyzer

For example, intelephense can show diagnostics in real time, there is no need to save the file to get new diagnostics. But rust-analyzer, the language server for rust, can only update diagnostics after saving the file.

6. Rust Analyzer

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