Eyal Z

On a second thought, I don’t know if std::bitset is enough here since it is for fixed size only, in that case I’ll consider adding support for `std::vector`, I’ll keep...

Hi, I can try to think what it might require to support bit fields but can’t you workaround the issue by serializing them as plain bytes, for example by bit...

Hi, Does this happen when using output archive only or also with input archive? For output I imagine you can manually construct a span and have no overhead by using...

I didn’t expect anyone to serialize a std::array of zero size, what is the goal you are trying to achieve by that?

If you use known sizes for fundamental types there is full compatibility, i.e std::uint32_t and friends. In practice int is almost always 4 bytes, char is always one byte. It’s...

Interesting, I will look into that. In the meantime I recommend to try and add a requires clause for each function for archive kind, or go for one function with...

Interesting case, since std::valarray is not directly part of the containers library in the standard the concepts don't apply to it. I will take a look, but this should be...

Try to put the serialize function in the same namespace as your type: https://godbolt.org/z/onqPYTTT6

I recommend to go for std::variant then use std::visit and work with them rather than using virtual. If you really want to use virtual then you need to implement a...

@david-sackstein 1. I added your change about read_zero and read_nonzero as separate overloads, then I realized there is no need to rename them, so both are named just "read", one...