File tree 1 file changed +4
-4
lines changed
1 file changed +4
-4
lines changed Original file line number Diff line number Diff line change @@ -662,7 +662,7 @@ pub unsafe fn read<T>(src: *const T) -> T {
662
662
///
663
663
/// An example of what not to do and how this relates to `read_unaligned` is:
664
664
///
665
- /// ```
665
+ /// ```no_run
666
666
/// #[repr(packed, C)]
667
667
/// struct Packed {
668
668
/// _padding: u8,
@@ -689,7 +689,7 @@ pub unsafe fn read<T>(src: *const T) -> T {
689
689
/// };
690
690
/// ```
691
691
///
692
- /// Accessing unaligned values directly with e.g. `packed.unaligned` is safe however.
692
+ /// Accessing unaligned fields directly with e.g. `packed.unaligned` is safe however.
693
693
// FIXME: Update docs based on outcome of RFC #2582 and friends.
694
694
#[ inline]
695
695
#[ stable( feature = "ptr_unaligned" , since = "1.17.0" ) ]
@@ -834,7 +834,7 @@ pub unsafe fn write<T>(dst: *mut T, src: T) {
834
834
///
835
835
/// An example of what not to do and how this relates to `write_unaligned` is:
836
836
///
837
- /// ```
837
+ /// ```no_run
838
838
/// #[repr(packed, C)]
839
839
/// struct Packed {
840
840
/// _padding: u8,
@@ -859,7 +859,7 @@ pub unsafe fn write<T>(dst: *mut T, src: T) {
859
859
/// };
860
860
/// ```
861
861
///
862
- /// Accessing unaligned values directly with e.g. `packed.unaligned` is safe however.
862
+ /// Accessing unaligned fields directly with e.g. `packed.unaligned` is safe however.
863
863
// FIXME: Update docs based on outcome of RFC #2582 and friends.
864
864
#[ inline]
865
865
#[ stable( feature = "ptr_unaligned" , since = "1.17.0" ) ]
You can’t perform that action at this time.
0 commit comments