Rename crate

[xoac]

Rename crate

[Kixunil]

How about binary_codec?

[Kixunil]

I definitely agree with not jumping on renaming too soon! I meant it more as a suggestion if the situation changes.

[chrysn]

packed-endian-struct, maybe (given that the serialization it produces doesn't have padding AFAICT)?

[xoac]

I would propose endian_codec and I decide to use _ after reading this issue

This will also change SerializeLittleEndain trait to EncodeLEetc. because the name was to long in practical use.

[wucke13]

Quite nice, that name! I suppose that both of you have a look of packed_struct. It looks like it is unmaintained, and the ergonomics are not super good (e.g. I wasn't able to get started in 20 minutes), however, feature wise it looks really complete & good.

[xoac]

Renaming create is still an option. But:

• it has to be much better name (not just better)
• crate has to be fully implemented

I think that the name is lacking of pack word so it could be pack_(with)_endian or struct_pack_endian, endian_packed packed_struct. I think pack should replace codec since it can pack and unpack objects what is a special case of codec.

I would at this moment vote against change the name. Why?:

• the crate is not supper important
• it's already published to crates.io
• crate can be found by adding category and keywords
  at this moment there are still free slots (and endian can be removed - it's in name)

    keywords = ["no_std", "endian", "bytes"]
    categories = ["no-std", "parsing"]
  

• This crate will be probably useful with no_std environment so I added it to awesome-emebedded-rust to be easier findable

I will not go with binary_codec - because can codec be done without binary?

I still think that endian is good part in name: Look at documentation:

just PackedSize don't contains endain in name. At it's just helping trait that I would be happy to hide from the end user.