Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Added a warning if conflicting rust-lang.rust is enabled. #6932

Merged
merged 2 commits into from Dec 18, 2020

Conversation

extremegf
Copy link
Contributor

Added a warning if conflicting rust-lang.rust plugin is enabled.

Resolves #6463

Screenshot from 2020-12-18 18-33-02

@lnicola
Copy link
Member

lnicola commented Dec 18, 2020

bors r+

@bors
Copy link
Contributor

bors bot commented Dec 18, 2020

@bors bors bot merged commit 53f81e4 into rust-lang:master Dec 18, 2020
@lnicola
Copy link
Member

lnicola commented Dec 18, 2020

Thanks!

@extremegf
Copy link
Contributor Author

My pleasure. I'm a big fan of RA!

@lnicola
Copy link
Member

lnicola commented Dec 21, 2020

Nb. in #6463 I said:

it might be worth checking that the current extension is matklad.rust-analyzer, though

This is because the plan is/was to integrate the rust-analyzer client code into the official extension. If that happens again, your code should be updated to actually check that both are installed.

And maybe we should also check for kalitaalexey.vscode-rust. That one appears to be gone from the marketplace, but I've seen someone using it in #6718.

Anyway, this is probably fine for now.

@extremegf
Copy link
Contributor Author

This is because the plan is/was to integrate the rust-analyzer client code into the official extension. If that happens again, your code should be updated to actually check that both are installed.

If rust-analyzer client code is integrated, I assume matklad.rust-analyzer will be dropped from the marketplace and replaced by rust-lang.rust. (Or do I misunderstund this process?)

In that case I could check if we are "matklad.rust-analizer" and if not silence the warning, so it doesn't pop up after integration, and log that this chceck can be removed.

And maybe we should also check for kalitaalexey.vscode-rust. That one appears to be gone from the marketplace, but I've seen someone using it in #6718.

I can check for it as well.

@lnicola
Copy link
Member

lnicola commented Dec 21, 2020

If rust-analyzer client code is integrated, I assume matklad.rust-analyzer will be dropped from the marketplace and replaced by rust-lang.rust. (Or do I misunderstund this process?)

The code is already there (under a configuration flag, but I don't think it works any more), and this extension still exist, so not necessarily 😄.

The simplest way would be to count whether more than one of rust-lang.rust, matklad.rust-analyzer and kalitaalexey.vscode-rust is installed. This would keep working (doing the right thing) even in rust-lang.rust, at the cost of duplicate warnings.

@extremegf
Copy link
Contributor Author

Ok, how about this? #7002

It detects any combination of conflicts.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

When loading VS Code extension, show a warning if rust-lang.rust is also installed
2 participants