diff options
| author | Dylan DPC <99973273+Dylan-DPC@users.noreply.github.com> | 2022-10-07 22:05:30 +0530 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2022-10-07 22:05:30 +0530 |
| commit | e461e94165e56be0b40d3916a0eb24745ea6e75c (patch) | |
| tree | 1c3a8fff4e5b62e519346ccd2ce6c057b4cce8c7 /compiler/rustc_llvm/llvm-wrapper/CoverageMappingWrapper.cpp | |
| parent | 25926095749ddc92b8b457383f8e129d267457e4 (diff) | |
| parent | c30dcff97a43292b729f384f847febe777daf629 (diff) | |
| download | rust-e461e94165e56be0b40d3916a0eb24745ea6e75c.tar.gz rust-e461e94165e56be0b40d3916a0eb24745ea6e75c.zip | |
Rollup merge of #102475 - RalfJung:unsafe, r=dtolnay
unsafe keyword: trait examples and unsafe_op_in_unsafe_fn update Having a safe `fn` in an `unsafe trait` vs an `unsafe fn` in a safe `trait` are pretty different situations, but the distinction is subtle and can confuse even seasoned Rust developers. So let's have explicit examples of both. I also removed the existing `unsafe trait` example since it was rather strange. Also the `unsafe_op_in_unsafe_fn` lint can help disentangle the two sides of `unsafe`, so update the docs to account for that.
Diffstat (limited to 'compiler/rustc_llvm/llvm-wrapper/CoverageMappingWrapper.cpp')
0 files changed, 0 insertions, 0 deletions