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

Implement UperReader for ScopedBitReader over Bits #81

Merged
merged 1 commit into from
Aug 5, 2023

Conversation

jkalez
Copy link
Contributor

@jkalez jkalez commented Aug 3, 2023

Previous implementations of UperReader required that a user have an implementation of Bits or a handful of other types (some primitives) in order to get a UperReader instance. However, the underlying implementation was designed to be generic over anything implementing ScopedBitReader. This commit removes the hard reliance on Bits in favor of being generic over ScopedBitReader. Users can now provide their own type implementing ScopedBitReader so and get their own implementation of UperReader. This is useful for streams of data which may not be easily represented as a Bits.

Previous implementations of UperReader required that a user have an
implementation of `Bits` or a handful of other types (some primitives)
in order to get a `UperReader` instance.  However, the underlying
implementation was designed to be generic over anything implementing
`ScopedBitReader`.  This commit removes the hard reliance on `Bits` in
favor of being generic over `ScopedBitReader`.  Users can now provide
their own type implementing `ScopedBitReader` so and get their own
implementation of `UperReader`.  This is useful for streams of data
which may not be easily represented as a `Bits`.
@kellerkindt
Copy link
Owner

Thanks!

@kellerkindt kellerkindt merged commit aa6b083 into kellerkindt:master Aug 5, 2023
@jkalez jkalez deleted the use_scoped_bit_read branch August 16, 2023 12:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants