Skip to content

How should I deal with disconnected DAGs? #26

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

Open
codesoap opened this issue Sep 24, 2022 · 0 comments
Open

How should I deal with disconnected DAGs? #26

codesoap opened this issue Sep 24, 2022 · 0 comments

Comments

@codesoap
Copy link

This is not necessarily a feature request, but I'm curious how you would deal with disconnected DAGs, or if this is outside the scope of this library. Currently the library does not enforce the graph to be connected, so I can have multiple disconnected DAGs within one DAG of the library. In this case some functions like DAG.GetRoots become less useful and there seems to be no way to find the roots of a specific vertex.

Do you think something like a func (d *DAG) GetConnectedDAGs() []*DAG or func (d *DAG) GetConnectedDAG(id string) *DAG or func (d *DAG) DeleteDisconnected(id string) or similar would be a good addition to the library?

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

No branches or pull requests

1 participant