rls does not respect cargo's target-dir config

[CrendKing]

Cargo has a config file that allows user to change the location of the target directory. It is done by adding the target-dir key under the build section. However, even after this is set and confirmed that cargo/rustc output to the new directory, rls will still use the default <project_root>/target/rls location for its own output.

Please either create a rls specific config to allow user to specify target directory location, or respect cargo's config.

[dbr]

I had this problem with rls 0.125.1-stable being used via VSCode integration

Could be mistaken, but looks like this might be fixed in #788 or #793

[Xanewok]

Fixed with #793, we can use „rust.target_dir” config option to specify desired target/ path for RLS.

Thanks @dbr!

[samuela]

I just came across this issue, but found that RLS only respects the target-dir config after restarting. It would be nice if this config change could be picked up by RLS reactively just like other config/code changes.