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
For instance, I think length calculations in message encoding are almost certainly bogus, since they're occuring in terms of the number of characters, not the number of bytes.
A possible workaround here is to write the string out to a byte array and see how many bytes we wrote, but this seems rather silly (and hopelessly inefficient). Nevertheless, there may not be a better alternative at this time.
Currently, the {read,write}UTF{,Bytes} methods are used. This may not always be sane.
The text was updated successfully, but these errors were encountered: