feat(go): use option for optional fields#3202
Merged
chaokunyang merged 22 commits intoapache:mainfrom Jan 26, 2026
Merged
Conversation
585f9e3 to
2a3a268
Compare
2a3a268 to
c394138
Compare
LiangliangSui
approved these changes
Jan 26, 2026
cf0e71c to
5d28d41
Compare
27eaa15 to
1c575a4
Compare
378e058 to
cef791d
Compare
6aefdea to
5a07e2b
Compare
58a8ba2 to
b26bd8b
Compare
b26bd8b to
a3dbaa5
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.
Why?
Align Go codegen/serialization with xlang optional field semantics and add cross-language coverage for optional IDL types.
What does this PR do?
optional.Optional[T](including decoder/encoder codegen, struct metadata, and type resolution) instead of pointers where supported.Related issues
Closes #3196
Does this PR introduce any user-facing change?
Benchmark