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

Incorrect warnings (Rust) #28

Open
DavidAntliff opened this issue Nov 12, 2024 · 4 comments
Open

Incorrect warnings (Rust) #28

DavidAntliff opened this issue Nov 12, 2024 · 4 comments

Comments

@DavidAntliff
Copy link

Using version 1.4.1 with RustRover 2024.4 EAP (243.20847.53).

Mostly working well, but occasionally gets confused:

image

These two spurious warnings only appear if the plugin is enabled.

Enabled:
image

Disabled:
image

To be clear, those two extra warnings only appear if the plugin is enabled.

Incidentally, there is no variable called physical_address in this file, but it does occur as a struct field in a different file.

And I'm not sure what's going on with that does not need to be mutable warning - there is no mutable variable there.

Let me know if there's more info I can provide.

@chylex
Copy link
Owner

chylex commented Nov 13, 2024

Does it happen consistently, i.e. if you re-enable the plugin do the spurious warnings appear again even after restarting RustRover?

@DavidAntliff
Copy link
Author

Yes, it seems persistent across IDE restarts, plugin disable/re-enable, as well as invalidate caches. It’s almost like it’s picking up warnings from other files and displaying them for the wrong file…

@chylex
Copy link
Owner

chylex commented Nov 13, 2024

Are the project sources available?

@DavidAntliff
Copy link
Author

Are the project sources available?

Unfortunately not with this project, but I'll keep an eye out for anything similar with any open-source projects I work on, and report back. If you'd prefer to close this issue now, that's cool - I can re-open it once I find another example.

(Note that I cleaned up all warnings from all files and these spurious warnings also disappeared, but I can't tell you when exactly that happened, sadly).

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

No branches or pull requests

2 participants