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
That's an interesting question. The binary or *view structures can encode any structured data one can describe, say, with JSONSchema. I use them as a simpler, js specific alternative to FlatBuffers for storage and transfer where JSON is too much of an overhead and the structures are too complex to just get away with a DataView or TypedArrays.
In case of HAMT, we can, for example, encode the resulting array of nodes as a VectorView (or several) of MapViews representing structures for nodes. This will essentially make the result immutable, since we cannot change the length of the created VectorView(s), and have some overhead depending on the way we describe the structures for nodes, though I'm sure it will be much less than most other ways of encoding will give us.
Could the binary structures serve as the basis for persistent data structures, implemented as HAMT?
The text was updated successfully, but these errors were encountered: