growable ringbuffer#92
Merged
Merged
Conversation
Owner
How do you mean "Index instead of Index", isize instead of usize? In any case also add the reasoning for the wrapper in a doc comment somewhere |
Owner
|
|
NULLx76
reviewed
Jun 5, 2023
jdonszelmann
force-pushed
the
growable-ringbuffer
branch
from
dfd3555 to
121acf5
Compare
This file contains hidden or 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
2 participants
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.
A wrapper around VecDeque with all ringbuffer traits implemented.
The reason it's a wrapper, is that RingBufferExt requires Index<isize> instead of Index<usize> which is something we cannot just override for the built in type.