You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the bytes are returned as ASCII / code points. That's not very useful; in most cases, it would be better to have a hex encoding such as provided by the hex package of the standard library.
The text was updated successfully, but these errors were encountered:
@rs I need this as well, I might end up working on a PR if we agree on the API.
My proposal is to add Hex8, Hex16, Hex32 and Hex64 wherever UintNN is used. The new hex functions would take uints of the specified size, but format then in hexadecimal format.
Currently, the bytes are returned as ASCII / code points. That's not very useful; in most cases, it would be better to have a hex encoding such as provided by the hex package of the standard library.
The text was updated successfully, but these errors were encountered: