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
We need to decide if we should break up the different types (sequences: list, tree, rope; kvmapping, etc.) into their own modules or keep them together. At minimum, though, we should put the type definitions into their own file to distinguish the metadata from the code. Like AdaptonTypes.ml, this will provide us with a way to pick out what types are available without other clutter.
The text was updated successfully, but these errors were encountered:
I've started on another version of spread tree, so far just called 'struct'. It may end up similarly needing to be broken up, but for now, this issue is on hold
@matthewhammer intends to work on this at some point, let me know if that changes. I'd suggest a single file structured similarly to the Trie code (SpreadTree.List(D : Data.S), SpreadTree.Rope(D : Data.S), etc), unless there's a compelling reason not to.
We need to decide if we should break up the different types (sequences: list, tree, rope; kvmapping, etc.) into their own modules or keep them together. At minimum, though, we should put the type definitions into their own file to distinguish the metadata from the code. Like AdaptonTypes.ml, this will provide us with a way to pick out what types are available without other clutter.
The text was updated successfully, but these errors were encountered: