-
Notifications
You must be signed in to change notification settings - Fork 1.6k
new lint: [readonly_write_lock
]
#11210
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
Conversation
r? @giraffate (rustbot has picked a reviewer for you, use r? to override) |
☔ The latest upstream changes (presumably #11115) made this pull request unmergeable. Please resolve the merge conflicts. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Overall looks good, thanks! I made some comments.
Co-authored-by: Takayuki Nakata <[email protected]>
@bors r+ Thanks! |
☀️ Test successful - checks-action_dev_test, checks-action_remark_test, checks-action_test |
uhh... did bors get stuck merging the PR or what happened here? 😅 |
Closes #8555
A new lint that catches
RwLock::write
calls to acquire a write lock only to read from it and not actually do any writes (mutations).changelog: new lint: [
readonly_write_lock
]