Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Divide up SpreadTree.ml into separate modules #10

Open
kyleheadley opened this issue Jan 14, 2015 · 2 comments
Open

Divide up SpreadTree.ml into separate modules #10

kyleheadley opened this issue Jan 14, 2015 · 2 comments

Comments

@kyleheadley
Copy link
Contributor

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.

@kyleheadley
Copy link
Contributor Author

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

@labichn
Copy link
Contributor

labichn commented Aug 6, 2015

@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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants