diff options
| author | bors <bors@rust-lang.org> | 2020-11-23 07:00:30 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2020-11-23 07:00:30 +0000 |
| commit | 068320b39e3e4839d832b3aa71fa910ba170673b (patch) | |
| tree | c019697eb36323b15719bf75d28410961ccaddcf /compiler/rustc_llvm/llvm-wrapper | |
| parent | 1823a87986c6acf0765c0101d75bca5328416a60 (diff) | |
| parent | 28f8e6244b3349b73ae9413fabaf6eb01c80807e (diff) | |
| download | rust-068320b39e3e4839d832b3aa71fa910ba170673b.tar.gz rust-068320b39e3e4839d832b3aa71fa910ba170673b.zip | |
Auto merge of #77893 - petertodd:2020-impl-default-for-phantompinned, r=dtolnay
Impl Default for PhantomPinned
`PhantomPinned` is just a marker type, with an obvious default value (the only value). So I can't think of a reason not to do this. Sure, it's used in exotic situations with unsafe code. But the people writing that code can decide for themselves if they can derive `Default`, and in many situations the derived impl will make sense:
```rust
#[derive(Default)]
struct NeedsPin {
marker: PhantomPinned,
buf: [u8; 1024],
ptr_to_data: Option<*const u8>,
}
```
Diffstat (limited to 'compiler/rustc_llvm/llvm-wrapper')
0 files changed, 0 insertions, 0 deletions
