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
commented
1 year ago
Previous implementations of
UperReaderrequired that a user have an implementation ofBitsor a handful of other types (some primitives) in order to get aUperReaderinstance. However, the underlying implementation was designed to be generic over anything implementingScopedBitReader. This commit removes the hard reliance onBitsin favor of being generic overScopedBitReader. Users can now provide their own type implementingScopedBitReaderso and get their own implementation ofUperReader. This is useful for streams of data which may not be easily represented as aBits.