Remove implicit Sized bound on Tree::range and others
#1499
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
…ange` and related methods.
Rafferty97
changed the title
Sized bound on Tree::range and othersSized bound on Tree::range and others
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.
See issue #1497.
The type parameter
Kon the methodTree::rangehas an implicitSizedconstraint, but it unnecessarily constrains the flexibility of the API. For example, it's not currently possible to callTree::rangewith a range ofRangeBounds<[u8]>as[u8]is not sized.Similar reasoning applies to the other two methods of
Treethat this PR adjusts in a similar fashion.