refactor(spec): remove language byte from xlang in protocol #3256
Conversation
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
pandalee99
approved these changes
Feb 3, 2026
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Why?
The xlang header no longer needs a per-language byte, and the ref-tracking naming has drifted across implementations. Align the protocol header and configuration to be consistent across languages.
What does this PR do?
xlangflag; language enums/constants removed where unused).track_ref/refacross languages and updates fingerprints, serializers, tests, and docs/specs.Related issues
#1017
Does this PR introduce any user-facing change?
Yes — the xlang wire header changes and ref-tracking/config naming updates are user-visible.
Benchmark