Review feedback

arrow/src/buffer/immutable.rs

@@ -187,7 +187,8 @@ impl Buffer {
     /// correctly for type `T`.
     pub fn typed_data<T: ArrowNativeType>(&self) -> &[T] {
         // SAFETY
-        // ArrowNativeType are trivially transmutable, and this method checks alignment
+        // ArrowNativeType is trivially transmutable, is sealed to prevent potentially incorrect
+        // implementation outside this crate, and this method checks alignment
         let (prefix, offsets, suffix) = unsafe { self.as_slice().align_to::<T>() };
         assert!(prefix.is_empty() && suffix.is_empty());
         offsets

arrow/src/buffer/mutable.rs

@@ -281,7 +281,8 @@ impl MutableBuffer {
     /// correctly for type `T`.
     pub fn typed_data_mut<T: ArrowNativeType>(&mut self) -> &mut [T] {
         // SAFETY
-        // ArrowNativeType are trivially transmutable, and this method checks alignment
+        // ArrowNativeType is trivially transmutable, is sealed to prevent potentially incorrect
+        // implementation outside this crate, and this method checks alignment
         let (prefix, offsets, suffix) =
             unsafe { self.as_slice_mut().align_to_mut::<T>() };
         assert!(prefix.is_empty() && suffix.is_empty());

arrow/src/datatypes/native.rs

@@ -42,7 +42,8 @@ pub trait JsonSerializable: 'static {
 ///
 /// Note: in the case of floating point numbers this transmutation can result in a signalling
 /// NaN, which, whilst sound, can be unwieldy. In general, whilst it is perfectly sound to
-/// reinterpret bytes as different types using this trait, it is likely unwise
+/// reinterpret bytes as different types using this trait, it is likely unwise. For more information
+/// see [f32::from_bits] and [f64::from_bits].
 ///
 /// Note: `bool` is restricted to `0` or `1`, and so `bool: !ArrowNativeType`
 ///