diff options
| author | bors <bors@rust-lang.org> | 2024-03-17 03:35:17 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2024-03-17 03:35:17 +0000 |
| commit | 67fa36a9f26e500b66b9221cff92b628ef3bb054 (patch) | |
| tree | 65f0e04b90764d6ab1598388c2b3d8daf3b092a9 /tests/coverage/branch/lazy-boolean.rs | |
| parent | 12ecaa836758c9257a9cb1682b31e1ef9108b396 (diff) | |
| parent | adcbb4a9b7427bdf508ec016961e999ed1d72612 (diff) | |
| download | rust-67fa36a9f26e500b66b9221cff92b628ef3bb054.tar.gz rust-67fa36a9f26e500b66b9221cff92b628ef3bb054.zip | |
Auto merge of #12479 - y21:readonly_write_lock_perf, r=Jarcho
move `readonly_write_lock` to perf [There haven't been any issues](https://github.com/rust-lang/rust-clippy/issues?q=is%3Aissue+readonly_write_lock) since its creation and it's a pretty useful lint I think, so I'd say it's worth giving it a try? Did a lintcheck run on 300 crates with no results, but I guess `RwLock` is usually not something that's used much in libraries. changelog: move [`readonly_write_lock`] to perf (now warn-by-default)
Diffstat (limited to 'tests/coverage/branch/lazy-boolean.rs')
0 files changed, 0 insertions, 0 deletions