Skip to content
This repository has been archived by the owner on May 31, 2018. It is now read-only.

optimize tsolver #652

Closed
rmarquis opened this issue Feb 11, 2017 · 3 comments
Closed

optimize tsolver #652

rmarquis opened this issue Feb 11, 2017 · 3 comments

Comments

@rmarquis
Copy link
Owner

rmarquis commented Feb 11, 2017

Merge SortDepsAur() with FindDepsAur(). These functions are virtually the same but were developed separately to minimize regression and ease testing.

The only purpose of the former is to prepare the tsort list and it can be done at the same time the tree is generated in the latter, resulting in a much faster solver.

@rmarquis
Copy link
Owner Author

Note: This isn't straightforward to do, and the deps solving algo might be simplified through refactoring. Have a look at bauerbill, since its solver implementation is very fast and is also the basic of aurutils.

@rmarquis
Copy link
Owner Author

Actually, the optimum solution here would be to have topological sorting with grouping, since the dependency tree is solved by "level" rather than by individual element.

I don't think this is possible to achieve with tsort though. Maybe there is a way to emulate that grouping feature through an abstraction layer?

@rmarquis
Copy link
Owner Author

rmarquis commented Jun 6, 2017

Dropping due to #708.

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

No branches or pull requests

1 participant