feat: continued bytesbuf tidying #132
Draft
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.
Updates API documentation with new and improved terminology. One step of many - further iterations for API docs improvement will follow.
Removes the requirement to go through
bytes::Bufandbytes::BufMuttraits when performing reads/writes onBytesBuf/BytesView. These traits are still implemented but now there are also equivalent inherent methods (sometimes with better signatures, no longer trying to maintain parity withbytesAPI signatures).In a later iteration, the
bytescompatibility traits will move behind a feature flag - not fully rooted out yet from all the places.Removes usage of
bytes::Bufandbytes::BufMutfrom examples, relying on inherentbytesbufmethods only.Improved panic documentation and assertion logic with regard to some obscure cases like exceeding
usize::MAX.