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.

Sign up for GitHub

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

Jump to bottom

Deprecate Algorithm base classes #118

Closed
clue opened this issue Jan 3, 2015 · 2 comments
Closed

Deprecate Algorithm base classes #118

clue opened this issue Jan 3, 2015 · 2 comments
Labels
help wanted maintenance

Comments

@clue
Copy link
Member

clue commented Jan 3, 2015

The abstract algorithm base classes are pretty much useless and make up for an awkward API (see also #94).

We should work towards updating the API of all algorithm implementations currently using the base classes and eventually remove the base classes.

Obviously, this involves quite a big BC break and will likely take some time until all algorithms are updated.
@clue
Copy link
Member Author

clue commented Jan 12, 2015

See #119.

@clue clue mentioned this issue Jan 22, 2015
Closed
@clue
Copy link
Member Author

clue commented Jan 22, 2015

Algorithms will be split off via #119, issue migrated to graphp/algorithms#5

@clue clue closed this as completed Jan 22, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
help wanted maintenance
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@clue