Remove tame-index
#58
Merged
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
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.
Rather than be tied to any specific crate (or worse, specific crate version), this removes the
prefer-indexfeature and the optional dependency ontame-indexin favor of just letting the user specify a simple callback that can be used to obtain the index metadata for a set of crates. This makes end usage a bit more tedious since you have to write that code yourself, but at the same time, it's mostly going to be a write once operation that means that you can bump versions of tame-index or crates-index or whatever without needing to wait on updates to this crate, or have duplicates in your dependency graph.