diff options
| author | bors <bors@rust-lang.org> | 2022-12-30 15:49:12 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2022-12-30 15:49:12 +0000 |
| commit | 6ccd4ebd5ba4d68dcfb56c8dea13b90c1d02a769 (patch) | |
| tree | 4a8360e733ad8f2379912f2bffaff34d2b27c6c4 /compiler/rustc_llvm/llvm-wrapper/CoverageMappingWrapper.cpp | |
| parent | 4f3ab69ea0a0908260944443c739426cc384ae1a (diff) | |
| parent | 0298095ac21e8fd5eb5ead8edc1b49a365972cc4 (diff) | |
| download | rust-6ccd4ebd5ba4d68dcfb56c8dea13b90c1d02a769.tar.gz rust-6ccd4ebd5ba4d68dcfb56c8dea13b90c1d02a769.zip | |
Auto merge of #10115 - rdrpenguin04:master, r=flip1995
Move `mutex_atomic` to `restriction` By #4295, the general consensus seems to be that `mutex_atomic` is not a useful lint in most cases. If anything, it could be useful as a restriction on code that for whatever reason can't use atomics. Keeping it in `clippy::nursery` is harmful to people attempting to use clippy for soundness. --- changelog: Moved [`mutex_atomic`] to `restriction` [#10115](https://github.com/rust-lang/rust-clippy/pull/10115) <!-- chnagelog_checked -->
Diffstat (limited to 'compiler/rustc_llvm/llvm-wrapper/CoverageMappingWrapper.cpp')
0 files changed, 0 insertions, 0 deletions