Skip to content

Inefficient bitstream #36

@beiriannydd

Description

@beiriannydd

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions