-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Easier readability for needless_late_init
message
#8779
Easier readability for needless_late_init
message
#8779
Conversation
r? @llogiq (rust-highfive has picked a reviewer for you, use r? to override) |
Thank you! @bors r+ |
📌 Commit 7017eb1 has been approved by |
Easier readability for `needless_late_init` message Closes #8530 Updated the lint to use a `MultiSpan`, showing where the `let` statement was first used and where the initialisation statement was done, as in the format described, for easier readability. Was wondering why, when pushing the span label for the initialisation statement, that sometimes the prior statement above the initialisation statement gets pulled into the output as well - any insight is appreciated!
💔 Test failed - checks-action_test |
The changelog entry was missing from the PR description. I've added it, now the CI should pass. @bors retry |
☀️ Test successful - checks-action_dev_test, checks-action_remark_test, checks-action_test |
Closes #8530
Updated the lint to use a
MultiSpan
, showing where thelet
statement was first used and where the initialisation statement was done, as in the format described, for easier readability.Was wondering why, when pushing the span label for the initialisation statement, that sometimes the prior statement above the initialisation statement gets pulled into the output as well - any insight is appreciated!
changelog: [
needless_late_init
]: Now shows thelet
statement where it was first initialized