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

When and what to report as resolution progresses #13

Open
uranusjr opened this issue Jan 31, 2020 · 2 comments
Open

When and what to report as resolution progresses #13

uranusjr opened this issue Jan 31, 2020 · 2 comments

Comments

@uranusjr
Copy link
Member

A stub issue to remind myself. Will first need to collect what exactly Cargo does first. A sensible default implementation using logging might be a good idea here as well.

@uranusjr uranusjr added this to Backlog in Resolver improvements Jan 31, 2020
@pradyunsg
Copy link
Contributor

suggestion: it might also be worth looking into https://github.com/CocoaPods/Molinillo and how CocoaPods uses it's "generic dependency algorithm".

@uranusjr uranusjr changed the title Learn from Cargo when and what to report as resolution progresses When and what to report as resolution progresses Feb 3, 2020
@uranusjr
Copy link
Member Author

uranusjr commented Feb 3, 2020

When debugging Molinilo fixtures I constantly add logging and breakpoints at three locations:

  • New candidate introduced (pinned).
  • Retracting a previously-pinned candidate due to backtracking.
  • A requirement exhausted all possible candidates, but cannot find a pin (which will trigger backtracking later).

So they are likely good reporting points.

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

No branches or pull requests

2 participants