Allow conflicting packages

[ejpcmac]

Since I updated atom-ide-rust to v0.17.0, I get a warning asking me to choose between atom-ide-rust and autocomplete-racer, even when I’m in a non-Rust project.

I know these packages are redundant on autocompletion, but I do use autocomplete-racer since RLS does not currently show documentation in code completion, and I find this is a really handy feature.

Possible workarounds

I see three possible workaround to this temporary* issue:

1. Warn only when in a Rust project. I can say “OK, I’m in the Rust context, there is a package conflict but I’m OK with it”. Outside of the Rust context it is just annoying to have such warning.

2. Add a “Keep both packages enabled” option. This would add an option in the config.cson to disable the warning.

3. A slightly different way to (2): add an option in the configuration to allow conflicting packages.

I personnally prefer the option (2), as it is straightforward for a user to dissmiss the warning and it affects only one conflicting package.

* the documentation in code completion should be come some day in RLS.

[alexheretic]

I agree that we could probably avoid this warning when not in a rust context. But it is useful to have the warning as soon as you install conflicting packages.

While option 2 is a nice experience for ignoring conflicts I really don't want to encourage doing so. These conflicts can cause errors that I want to avoid see #82.

If it's useful why not just add docs to rls-racer completion?

...10 minutes of work gets:

[ejpcmac]

If it's useful why not just add docs to rls-racer completion?

...10 minutes of work gets:
[...]

Oh, sweet! Should I build my own RLS to do this? This solution would be indeed a far more correct answer to my problem.

[alexheretic]

I'll raise a pr for the doc completion in a sec.

I think we can also do option-1, ie not check until ide-rust has at least started one rls instance, this will avoid people having to deal with this when they're not rusting.

[ejpcmac]

I'll raise a pr for the doc completion in a sec.

Thanks very much!

I think we can also do option-1, ie not check until ide-rust has at least started one rls instance, this will avoid people having to deal with this when they're not rusting.

This seems to be a sane approach indeed.

[alexheretic]

rust-lang/rls#903