-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Duplicate "remove unnecessary parentheses" code action #15801
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
Comments
One of them is a code assist that rust-analyzer is generating out of the output of a compiler warning (run The rust-analyzer one is even broken in some cases: fn main() {
match(true) {}
} Becomes: fn main() {
matchtrue {}
} Which is of-course invalid. Maybe getting rid of the built-in rust-analyzer assist would be a better idea than trying to fix it? I don't know how much the built-in rust-analyzer code-assist and the compiler suggestions overlap in terms of functionality |
The built-in diagnostic works on-the-fly, without saving the file. Why should we get rid of it? |
Good point, haven't thought of that, thought it was simply redundant |
Created a separate ticket #15844 to address the issue I mentioned |
Let's close this, I don't think we can do much else about it. |
rust-analyzer version: 2023-10-16
rustc version: rustc 1.73.0 (cc66ad468 2023-10-03)
The text was updated successfully, but these errors were encountered: