So after skimming the paper, this seems like a formalization of something like Protobuf/CaptnProto with native language support.
Interesting, but not necessarily very practical.
Interesting, but not necessarily very practical.
CapnProto is a wonderful library interface for dealing with serialized data, but I think the usual library-vs-compiler distinction applies. A library operates at the level of individual data access methods, but it doesn't try to change the control flow of the code calling those methods.
That's our goal with this project. We sometimes turn the code a bit inside out in order to make it better operate on serialized data. (For instance, switching a postorder traversal to a preorder one.)