UNHEX now returns []byte #619
Merged
Conversation
This file contains 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
zachmu
approved these changes
Nov 11, 2021
| tf.AddSucceeding("\x8f", "8F") | ||
| tf.AddSucceeding("\x8f", "8f") | ||
| tf.AddSucceeding("\x0b", "B") | ||
| tf.AddSucceeding([]byte{0x4d, 0x79, 0x53, 0x51, 0x4c}, "4D7953514C") |
There was a problem hiding this comment.
Probably easiest to just []byte() on the string of hex value, rather than using the ascii code points here
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Tests have been adjusted to reflect this change
Added another case in function_test for []byte