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
Since this is several years old, it seems to have missed the fact that msgpack has included distinct codes and encodings for strings and byte arrays for a while now (1). Current msgpack impls support the spec in this regard. Further, the codes used in binarypack conflict with those used in msgpack for these purposes. Should binarypack be deprecated and binaryjs made to use a current msgpack impl? Or at very least, binarypack should be made compatible with current spec.
Since this is several years old, it seems to have missed the fact that msgpack has included distinct codes and encodings for strings and byte arrays for a while now (1). Current msgpack impls support the spec in this regard. Further, the codes used in binarypack conflict with those used in msgpack for these purposes. Should binarypack be deprecated and binaryjs made to use a current msgpack impl? Or at very least, binarypack should be made compatible with current spec.
The text was updated successfully, but these errors were encountered: