diff options
| author | bors <bors@rust-lang.org> | 2022-04-04 13:07:26 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2022-04-04 13:07:26 +0000 |
| commit | 190f0deac83174de23ff21f980ab514c90e0e59e (patch) | |
| tree | 06e50a0aaee1ff8d5d35c4d6fd1b7f3e224b481d /tests/codegen/src-hash-algorithm | |
| parent | 1cec8b30fac2c13504de7e7f950bd36c497858b1 (diff) | |
| parent | 17c8bee95a43cf9c39ec766cdaa8c6219f4126dd (diff) | |
| download | rust-190f0deac83174de23ff21f980ab514c90e0e59e.tar.gz rust-190f0deac83174de23ff21f980ab514c90e0e59e.zip | |
Auto merge of #8450 - Jarcho:unsafe_blocks_8449, r=giraffate
Rework `undocumented_unsafe_blocks`
fixes: #8264
fixes: #8449
One thing came up while working on this. Currently comments on the same line are supported like so:
```rust
/* SAFETY: reason */ unsafe {}
```
Is this worth supporting at all? Anything other than a couple of words doesn't really fit well.
edit: [zulip topic](https://rust-lang.zulipchat.com/#narrow/stream/257328-clippy/topic/.60undocumented_unsafe_blocks.60.20same.20line.20comment)
changelog: Don't lint `undocumented_unsafe_blocks` when the unsafe block comes from a proc-macro.
changelog: Don't lint `undocumented_unsafe_blocks` when the preceding line has a safety comment and the unsafe block is a sub-expression.
Diffstat (limited to 'tests/codegen/src-hash-algorithm')
0 files changed, 0 insertions, 0 deletions