You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
pogs structs should be able to insert and extract data from a struct that it does not have an explicit field for (whether that be from an omitted struct field or receiving a newer copy of the struct). This would enable read-modify-write scenarios while still preserving unknown fields.
Based on a conversation with Kenton, the way this ought to work is to allow a field that has a capnp.Struct pointer back to the original data, and then on Insert, read from it to scoop up any unknown fields.
The text was updated successfully, but these errors were encountered:
pogs structs should be able to insert and extract data from a struct that it does not have an explicit field for (whether that be from an omitted struct field or receiving a newer copy of the struct). This would enable read-modify-write scenarios while still preserving unknown fields.
Based on a conversation with Kenton, the way this ought to work is to allow a field that has a
capnp.Struct
pointer back to the original data, and then onInsert
, read from it to scoop up any unknown fields.The text was updated successfully, but these errors were encountered: