Note that Cap'n Proto's mutability limitations are inherent to being a zero-copy protocol -- it's necessary to allocate messages in contiguous memory, tightly p

Note that Cap'n Proto's mutability limitations are inherent to being a zero-copy protocol -- it's necessary to allocate messages in contiguous memory, tightly packed, which makes it hard to be able to allocate memory dynamically. NoProto also claims to be zero-copy, which would seem to subject it to the same issues. I couldn't find anything in the docs explaining how they avoid it.