bitser
bitser copied to clipboard
allow VLA serialization with t=254
This solves issue #27
I can add your proposed pcall solution for issue #25 if you wish.
Type IDs are going to conflict very soon :( Should some "extended type ID marker" be assigned soon? As in, if 254/255, the next byte is a new type id. effectively giving 255 more free IDs
I would like to see if I can fold VLAs and VLSs into type code 252 first.
@adriweb Yes, in my head I'd already reserved type code 255 for some kind of "extended type" thing. I'm not sure what the semantics of it are going to be yet.