refactor: align MsgPackOpCode cases with MessagePack formats - #20
Merged
Conversation
nnabeyang
force-pushed
the
refactor/msgpack-opcode-init
branch
from
July 21, 2026 23:10
2a31d41 to
5752817
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
MsgPackOpCodepreviously grouped nil, boolean, and floating-point formats under an implementation-specific.simplecase and classified fix formats through nested bitmask conditions. Replace.simplewith dedicated.nil,.bool, and.floatcases, update eager and lazy scanning paths to handle them directly, and rewrite the initializer as a single range-based switch that follows the MessagePack opcode table.