refactor: introduce cached schema extension metadata - #359
Draft
jterapin wants to merge 11 commits into
Draft
Conversation
This was referenced Sep 3, 2026
jterapin
force-pushed
the
serde-opt/1-serde
branch
from
September 8, 2026 23:28
d09927e to
d17dad3
Compare
jterapin
force-pushed
the
serde-opt/1-serde
branch
from
September 8, 2026 23:37
d17dad3 to
509e4f7
Compare
jterapin
force-pushed
the
serde-opt/1-serde
branch
from
September 9, 2026 21:22
e594596 to
c7e3cf0
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
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.
Context
Shape and member metadata is currently resolved through multiple lookups and separate cache entries. This causes parsers, builders, and protocol code to rediscover related metadata.
What changed
for(shape)andfor_member(member)resolution paths.add_member.Out of scope
Testing
613 examples, 0 failures.