byteorder

this assertion is not universally correct, unfortunately: https://github.com/BurntSushi/byteorder/blob/1.5.0/src/lib.rs#L1271 u64 has a higher alignment than f64 on AIX. The alignment for f64 is currently misreported by Rust as equal to u64 on AIX for deeply convoluted reasons that require multiple levels of compiler fixes. cc @amy-kwan

hello, thank you for your contribution in this project, I am scanning the unsoundness problem in rust project. I notice the following code: https://github.com/BurntSushi/byteorder/blob/5a82625fae462e8ba64cec8146b24a372b4d75c6/src/lib.rs#L1408 In my opinion, write_i16_into is a function in lib.rs that can be directly accessed by user. src can be assigned any i16 type, which may result in UB when performing the unsafe operation "slice::from_raw_parts(src.as_ptr() as *const u16, src.len()) };" (eg. if src is an invaild address). Since this is a library published on crate.io, I thought it might be worth reporting this issue. Because according to Rust's safety spec, any code that could cause UB should be marked as unsafe. I chose to report them for safety reasons.