-
Notifications
You must be signed in to change notification settings - Fork 69
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
Multitree #268
Comments
Interesting, it's the first time I hear about multitrees. Since multitrees are graphs with a special structure, you can use the library to work with multitrees as long as you don't need to capture this special structure at the type level, or exploit the structure to implement some of the algorithms faster. Do you have anything specific in mind? |
Yea, I've never heard of it before either. I've been using the term heterarchy, but "multitree" is probably more suitable for those cases.
I think I'll have concrete ideas when I get to reimplement grit in Haskell (unless I choose F#!), which I'd like to do as I've been mulling over a structured task manager for a long time now! |
Right, I see. If you come across any specific issues with this library feel free to get in touch. In general, my goal is to eventually make the library more lightweight and get rid of some of the functionality (perhaps, by moving it to separate libraries), rather than to add more exotic features to it. |
Are multitrees in scope for this library?
It is basically a DAG with certain constraints.
Here's an explanation of, and a use case for, multitrees: https://github.com/climech/grit#multitrees
The text was updated successfully, but these errors were encountered: