Add an upgrade section #6
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| pub trait DependencyProvider<P: Package, V: Version> { | ||
| /// Compute the priority of a given package and range of versions for the solver. | ||
| /// When deciding which package to pick next, the solver will choose the highest priority one. | ||
| fn prioritize(&self, package, version_set) -> // priority |
There was a problem hiding this comment.
It could help to include an example of the types that might be commonly used for Priority.
|
@konstin, I kind of forgot about this PR in our ongoing work to release 0.3 (sorry @mpizenberg) is any of it still useful and helpful? Perhaps if not here in the change log? |
|
yes we can recycle some of that for the changelog |
|
Please take it over, I don’t have much time to work on this. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is the first in a series of PRs that are intended to be merged into the
v03branch of this guide repo.Once all v03 guide upgrades are done, we can merge it all into the main branch and deploy.
This PR adds a section describing the differences between v0.2 and v0.3 such that people understand what they have to update in their code.