-
Notifications
You must be signed in to change notification settings - Fork 4
Open
Description
Whilst this implementation isn't invalid, it isn't in keeping with the principle of msgpack in that it doesn't encode to the smallest bitstream. Efficiencies could be gained by using the smallest storage for the value being stored, not the variable it came from.
An int16(0) is not being represented in bitstream as [0], but rather as [d1,0,0]. The value should be placed into the bitstream as "a number" and then converted back to whatever the developer wants to store "the number" in.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels