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
Flatbuffers could be serialized into byte slices of a table, thereby nesting the flatbuffer. In the main rust flatbuffer implementation, this is not supported without having to copy a finished flatbuffer in, but in C++ it is.
It would be cool to support this.
The text was updated successfully, but these errors were encountered:
This is in principle not hard to support, but in practice it requires a bit of thought.
For instance, do we want to prevent the foot-gun of mixing in stuff not meant to go into the nested table? I think allowing that is too large a footgun for me to be comfortable with it (both in terms of performance and in terms of leaking unintended data).
I am thinking that maybe we can do something like this?
Flatbuffers could be serialized into byte slices of a table, thereby nesting the flatbuffer. In the main rust flatbuffer implementation, this is not supported without having to copy a finished flatbuffer in, but in C++ it is.
It would be cool to support this.
The text was updated successfully, but these errors were encountered: