Addressing binary serialization for db types

[NikVolf]

for interprocess messages, all arguments types must support FromRawBytesVariable and ToBytesWithMap traits

simple fixed-size structs are auto-implemented with sized_binary_map! macro, while structures containing heap-allocated vectors of data need to stick to several pre-mapped tuples

[arkpar]

Member struct can't be used for IPC?

[NikVolf]

need to move it to seraparate struct BranchBecomingCanonChainData to represent it later as a tuple to use in generic serializer
impl<'a, V1, V2, T3> ToBytesWithMap for (&'a Vec<V1>, &'a Vec<V2>, &'a T3)

otherwise you need to write full serialization for the whole struct BlockLocation by hand

[gavofyork]

can the struct's serialisation code not be autogenerated?

[NikVolf]

@gavofyork yes, one can provide custom implementation of ToBytesWithMap & FromRawBytesVariable, but you will have to do it for the whole struct

[gavofyork]

one can provide custom implementation

can this "custom implementation" not be autogenerated by the compiler plugin?

[NikVolf]

@gavofyork
yes this is possible, but it will take some time and will be targeted by future prs
the idea is to generate code that will write/read structs directly to/from nanomsg buffers and to achieve zero-copy messaging
and this is kind of temporal solution

[arkpar]

Consider using ElasticArray instead of Vec<u8> for serialization