I hope to be able to clearly indicate whether a struct is big-endian or little-endian.

[lethargy123]

I think a macro like #[zerocopy(little)] could be used to specify the endianness, so that for large structs there’s no need to use byteorder to indicate byte order. This would make it easier to quickly migrate code from other binary libraries to zerocopy.

[joshlf]

Can you provide an example of what this attribute would do? Would it take an existing struct definition and modify the struct's fields or layout somehow?

[lethargy123]

你能举个例子说明这个属性会起什么作用吗？它会用现有的结构定义，然后以某种方式修改结构体的字段或布局吗？

For example, there is a struct like this:

#[derive(IntoBytes)]
#[repr(C, packed)]
pub struct ABC {
a: u32,
b: u8,
}

If I need to specify the byte order, the current API implementation should look like this:

use zerocopy::byteorder::little_endian::*;
#[derive(IntoBytes)]
#[repr(C, packed)]
pub struct ABC {
a: U32,
b: u8,
}

However, the more convenient approach I envision would be like this:

#[derive(IntoBytes)]
#[repr(C, packed)]
#[zerocopy(little)]
pub struct ABC {
a: u32,
b: u8,
}

I believe this API change would have minimal impact on existing code, as it would only require adding new macro support to zerocopy_derive.