Serde Serialize/Deserialize implementation? about bitvec HOT 5 CLOSED

from bitvec.

from bitvec.

I think I have a reasonable concept of how to accomplish this.

Fundamentally, a BitSlice is composed of two structures:

• the handle: a (magically packed) structure of pointer (useless), element count (necessary), head position (necessary), and tail position (necessary)
  • the type parameters C: Cursor and T: Bits also need to be de/serialized somehow
• the data: a sequence of arbitrary T elements.

The following RON is probably a reasonable representation:

BitSlice {
 cursor: "BigEndian" | "LittleEndian" | other?,
 storage: "u8" | "u16" | "u32" | "u64",
 elements: usize,
 head: u8,
 tail: u8,
 data: [
  number,
  number,
 ],
}

I am not entirely sure how the cursor and storage parameters will work, but I'll cross that bridge later. In the meantime, this is the data model I'm going to try out and see how it goes.

from bitvec.

@djahandarie does commit 7b466d7 address what you want?

edit: rebased master to move a bugfix to the bottom of my unpublished history, changing the commit ID that implements serdes.

from bitvec.

bitvec 0.11.0 contains a serde feature which enables serialization of BitSlice in all environments, and de/serialization of BitBox and BitVec when an allocator exists.

from bitvec.