[Variant] feat: Support typed_access for Boolean #8346
Merged
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
Weijun-H
force-pushed
the
8329-type-access-for-boolean
branch
from
31de181 to
f873465
Compare
Weijun-H
force-pushed
the
8329-type-access-for-boolean
branch
from
f873465 to
3fa4c4d
Compare
Weijun-H
changed the title
codephage2020
approved these changes
Sep 15, 2025
| ]); | ||
|
|
||
| let struct_array = StructArrayBuilder::new() | ||
| .with_field("metadata", Arc::new(metadata)) |
Contributor
There was a problem hiding this comment.
It's worth noting that Once this PR is merged, it should be rewritten.
Contributor
There was a problem hiding this comment.
Thank you -- I will resolve the conflict
mbrobbel
approved these changes
Sep 15, 2025
Contributor
|
🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 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.
Which issue does this PR close?
Boolean#8329.Rationale for this change
What changes are included in this PR?
Are these changes tested?
Yes
Are there any user-facing changes?
If there are user-facing changes then we may require documentation to be updated before approving the PR.
If there are any breaking changes to public APIs, please call them out.