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
I guess when implementing string support, char support might come as a by-product, since the string already has to handle unicode encoding/decoding. Or if you go for byte[] transfer, then a char could be converted into a byte[2] for transport with the same logic I guess.
Though not a high priority issue.
The text was updated successfully, but these errors were encountered:
As discussed here: #4 (comment)
I guess when implementing string support, char support might come as a by-product, since the string already has to handle unicode encoding/decoding. Or if you go for byte[] transfer, then a char could be converted into a byte[2] for transport with the same logic I guess.
Though not a high priority issue.
The text was updated successfully, but these errors were encountered: