Don't expect valid UTF-8 when decoding or encoding #11
Conversation
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
brycx
changed the title
brycx
force-pushed
the
decode_to_bytes
branch
from
e6920c9 to
a9afd22
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Changes
decode()to returnVec<u8>andencodeto take&[u8], to comply fully with the specification. I think it's worth adding this as a breaking change (changed function signatures), since this was, strictly speaking, non-compliance with the specification.Probably needs more work @return, let me know what you think of the API changes.
TODO: Ensure README examples and docs are up-to-date.Closes #10