feat(binding/go): expose all write options#7647
Merged
Merged
Conversation
dosubot
Bot
added
size:XL
Member
Author
dentiny
changed the title
dentiny
changed the title
dentiny
force-pushed
the
hjiang/expose-write-options
branch
from
2b68507 to
315c9d7
Compare
dentiny
force-pushed
the
hjiang/expose-write-options
branch
from
315c9d7 to
e76d146
Compare
dentiny
changed the title
yuchanns
reviewed
Jun 1, 2026
FrankYang0529
approved these changes
Jun 1, 2026
Member
Author
|
Plan to merge this -- @FrankYang0529 and I will followup with delete and read with options. |
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
3 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.
Rationale for this change
golang and C binding should be compatible with rust core functionality-wise.
What changes are included in this PR?
This PR exposes all rust write options to C and go binding, which could be useful together with list and stats operation (for example, #7645).
Are there any user-facing changes?
Yes, new write option is exposed.
AI Usage Statement
GPT-5.5 helped me make the code change, GPT-5.5 and opus-4.8 did the code review.