-
Notifications
You must be signed in to change notification settings - Fork 105
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
Split ByteSlice::split_at into separate trait #1
Labels
compatibility-breaking
Changes that are (likely to be) breaking
Comments
joshlf
added
the
blocking-next-release
This issue should be resolved before we release on crates.io
label
Oct 15, 2022
Closed
joshlf
added
compatibility-breaking
Changes that are (likely to be) breaking
and removed
blocking-next-release
This issue should be resolved before we release on crates.io
labels
Aug 12, 2023
joshlf
added a commit
that referenced
this issue
Mar 1, 2024
TODO: - Consider making these traits un-sealed - Implement ByteSlice and ByteSliceMut for Vec<u8> Closes #1
This was referenced Mar 1, 2024
joshlf
added a commit
that referenced
this issue
Mar 1, 2024
joshlf
added a commit
that referenced
this issue
Mar 1, 2024
joshlf
added a commit
that referenced
this issue
Mar 1, 2024
1 task
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Migrated from https://fxbug.dev/76635
Currently, we don't implement
ByteSlice
forVec<u8>
because it would be expensive to implement thesplit_at
method. However, most uses ofByteSlice
don't make use of this method. We should splitByteSlice
into multiple traits and only use the trait with thesplit_at
method where it's actually necessary.Vec
can then implement the base trait but not the trait with thesplit_at
method.Possible names for these traits:
ByteSlice
andSplittableByteSlice
.The text was updated successfully, but these errors were encountered: