rust/zerocopy/src/pointer/transmute.rs
Source file repositories/reference/linux-study-clean/rust/zerocopy/src/pointer/transmute.rs
File Facts
- System
- Linux kernel
- Corpus path
rust/zerocopy/src/pointer/transmute.rs- Extension
.rs- Size
- 20831 bytes
- Lines
- 523
- Domain
- Rust Kernel Layer
- Bucket
- Rust API Membrane
- Inferred role
- Rust Kernel Layer: implementation source
- Status
- source implementation candidate
Why This File Exists
Rust-side wrappers and abstractions around kernel C APIs, ownership contracts, allocation, synchronization, and module integration.
- Rust-side wrappers and abstractions around kernel C APIs, ownership contracts, allocation, synchronization, and module integration.
- Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.
Dependency Surface
- No C-style include directives detected by the generator.
Detected Declarations
function test_transmute_coverage
Annotated Snippet
fn test_transmute_coverage() {
// SizeEq<T> for MaybeUninit<T>
test_size_eq::<u8, MaybeUninit<u8>>(0u8);
// SizeEq<MaybeUninit<T>> for T
test_size_eq::<MaybeUninit<u8>, u8>(MaybeUninit::<u8>::new(0));
// Transitive: MaybeUninit<T> -> Wrapping<T>
// T => MaybeUninit<T> => T => Wrapping<T>
test_size_eq::<u8, Wrapping<u8>>(0u8);
// T => Wrapping<T> => T => MaybeUninit<T>
test_size_eq::<Wrapping<u8>, MaybeUninit<u8>>(Wrapping(0u8));
// T: ?Sized => Cell<T> => T => UnsafeCell<T>
test_size_eq::<Cell<u8>, UnsafeCell<u8>>(Cell::new(0u8));
// T: ?Sized => UnsafeCell<T> => T => Cell<T>
test_size_eq::<UnsafeCell<u8>, Cell<u8>>(UnsafeCell::new(0u8));
}
}
Annotation
- Detected declarations: `function test_transmute_coverage`.
- Atlas domain: Rust Kernel Layer / Rust API Membrane.
- Implementation status: source implementation candidate.
Implementation Notes
- This generated page is the file-by-file coverage layer; curated subsystem chapters should link here when they synthesize a multi-file control flow.
- Core OS pages should be promoted from atlas-only to deep-reviewed when they explain data structures, invariants, locking, lifecycle, and C implementation snippets.
- Driver-family pages are intentionally pattern-oriented unless they are part of the selected PCIe/NVMe representative device path.