Skip to content

Make flycheck diagnostics track their generation #19854

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

Open
Veykril opened this issue May 23, 2025 · 0 comments
Open

Make flycheck diagnostics track their generation #19854

Veykril opened this issue May 23, 2025 · 0 comments
Labels
A-flycheck issues with flycheck a.k.a. "check on save" C-bug Category: bug

Comments

@Veykril
Copy link
Member

Veykril commented May 23, 2025

Noting this down before I forget again. This was sparked by a RustWeek discussion.

We should make flycheck diagnostics generational after all. Why? Because there seem to be setups where cargo may not report an artifact to our runner at all, causing us to not record an event for a crate which ultimately may result in us not clearing diagnostics in a given crate. This has manifested a couple times for me already, in part getting so bad that there are diagnostics that never get cleared at all. This is obviously not great.

So the idea would be to clear all diagnostics of a differing generation than the current if flycheck completes successfully.

@Veykril Veykril added C-bug Category: bug A-flycheck issues with flycheck a.k.a. "check on save" labels May 23, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-flycheck issues with flycheck a.k.a. "check on save" C-bug Category: bug
Projects
None yet
Development

No branches or pull requests

1 participant