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
The current design assumes that any string that is valid hex is intended to a binary string. This means it's not possible to encode such strings as regular strings, e.g. "1234".
Would it be possible to make this behavior optional? opt-in ideally, or opt-out.
Thanks.
The text was updated successfully, but these errors were encountered:
That is an early design choice as the most useful to my circumstances. Yes I have been bitten by that choice a few times, unlikely scenarios are more common in practice.
Unfortunately(to my knowledge) there is no good typing in emacs to separate a unibytestring and multibyte one. I have sometimes suffered from a string changing between the two during normal use.
I once tried having the byte-string wrapped in a struct. But that complicates the minimal design of this package and to my case, it didn't help much. In the end hex-string and normal string can equally hold information, and that is good enough for me. And if I really need it to be a string some white space padding does the trick for me, way better than anything else.
Of course, feel free to fork the project and give it a try yourself. If I like your approach, I might steal it back into the project. That is the rule of GPLv3.
The current design assumes that any string that is valid hex is intended to a binary string. This means it's not possible to encode such strings as regular strings, e.g.
"1234"
.Would it be possible to make this behavior optional? opt-in ideally, or opt-out.
Thanks.
The text was updated successfully, but these errors were encountered: