Integrate with RLS

[damienmg]

I am working with VSCode and while it is super nice with Rust & Cargo, RLS bugs out with Bazel. I am actually contemplating shaving that yak further and modifying RLS and VSCode RLS to support generic build system but I have resisted the temptation so far so I am creating a bug here so it doesn't get lost.

Might be a workaround to use #71.

[mfarrugi]

If there's not a way better than #71, I am happy to polish it up. I've been using intellij-rust and don't think it's worth trying to fix all of the things downstream of Cargo.toml`s

…

On Fri, Jun 8, 2018, 16:46 Damien Martin-Guillerez ***@***.***> wrote: I am working with VSCode and while it is super nice with Rust & Cargo, RLS bugs out with Bazel. I am actually contemplating shaving that yak further and modifying RLS and VSCode RLS to support generic build system but I have resisted the temptation so far so I am creating a bug here so it doesn't get lost. Might be a workaround to use #71 <#71>. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#95>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ACLjeOebODU7ZdkWWQWmR0tbdQi1s8uVks5t6uKugaJpZM4Ug7gB> .

[damienmg]

#71 would only provide a workaround by generated a file, you would still need to generate that file or use ibazel to do so... Maybe #71 and ibazel would be good enough though. I should try it ;)

[damienmg]

Ok so I think #71 and bazel-watcher is going to make an acceptable solution. Not as nice as getting RLS to understand other build system (although seeing RLS code, that shouldn't be too hard) but it seems to be the more straightforward version. I'll leave some more comment about the prototype on #71.

[damienmg]

I digged a bit more in RLS source code and they basically runs cargo to get the list of rustc call it perform (see https://github.com/rust-lang-nursery/rls/blob/master/src/build/cargo.rs#L332). This should be quite easy to adapt to Bazel except that the current rust files create a symlink tree that is not exposed. This could be done by simply moving the setup_cmd in a separate command that would output a directory artifact. So the rustc execution would all be a single command.

I actually don't follow why we need to do all that set-up, why can't we point rustc to the deps directly? I reviewed that original code but I was knowing nothing of rust at that time.

[damienmg]

Ok there is one reason we might want to put all deps in one dir is to avoid explosion in the command line size but there is a standard way to fix that is by using params file. It seems like rustc does not support it at the moment but I am pretty sure it wouldn't be hard to upstream that.

[damienmg]

I'll probably tackle this during my next flight (this week).

My current plan is to use bazel aquary to generate a build plan and pass it to RLS. RLS support getting a JSON build plan (see cargo build --build-plan) from a custom command (specified as part of RLS config here: https://github.com/rust-lang-nursery/rls/blob/master/src/config.rs#L165).

[mfarrugi]

@damienmg why is this approach preferable to generating the Cargo.toml? If we do that, we should be able to have cargo run the RLS under a bazel workspace as well.

[damienmg]

This approach is simpler than generating the toml file (that we don't have at the moment) and support generated file. The build by RLS would be driven by Bazel.

[beefsack]

Perhaps integrating with rust-analyzer would be easier at the moment. rust-analyzer is part of a larger rls-2.0 effort and already has some build system agnostic functionality.

[dayfine]

So what's the recommended way now to have RLS in VSCode works with Bazel?

[purkhusid]

Anybody got anything that works OK?