Skip to content

introduce take_n_true benchmark - #10703

Merged
Jefffrey merged 3 commits into
apache:mainfrom
Rich-T-kid:rich-T-kid/take_n_true_bench
Aug 16, 2026
Merged

introduce take_n_true benchmark#10703
Jefffrey merged 3 commits into
apache:mainfrom
Rich-T-kid:rich-T-kid/take_n_true_bench

Conversation

@Rich-T-kid

@Rich-T-kid Rich-T-kid commented Aug 16, 2026

Copy link
Copy Markdown
Contributor

Which issue does this PR close?

Rationale for this change

see #10438 (comment)

What changes are included in this PR?

adds benchmarks for BooleanArray::take_first

Are these changes tested?

n/a

Are there any user-facing changes?

no

@github-actions github-actions Bot added arrow Changes to the arrow crate arrow-array labels Aug 16, 2026
@Jefffrey Jefffrey added the development-process Related to development process of arrow-rs label Aug 16, 2026
@Jefffrey
Jefffrey merged commit d67185b into apache:main Aug 16, 2026
35 checks passed
@Jefffrey

Copy link
Copy Markdown
Contributor

thanks @Rich-T-kid

MassivePizza pushed a commit to massive-com/arrow-rs that referenced this pull request Aug 19, 2026
# Which issue does this PR close?

<!--
We generally require a GitHub issue to be filed for all bug fixes and
enhancements and this helps us generate change logs for our releases.
You can link an issue to this PR using the GitHub syntax.
-->

- works towards closing apache#10251.
- related to apache#10438

# Rationale for this change
see
apache#10438 (comment)

<!--
Why are you proposing this change? If this is already explained clearly
in the issue then this section is not needed.
Explaining clearly why changes are proposed helps reviewers understand
your changes and offer better suggestions for fixes.
-->

# What changes are included in this PR?
adds benchmarks for `BooleanArray::take_first`
<!--
There is no need to duplicate the description in the issue here but it
is sometimes worth providing a summary of the individual changes in this
PR.
-->

# Are these changes tested?
n/a
<!--
We typically require tests for all PRs in order to:
1. Prevent the code from being accidentally broken by subsequent changes
2. Serve as another way to document the expected behavior of the code

If tests are not included in your PR, please explain why (for example,
are they covered by existing tests)?

If this PR claims a performance improvement, please include evidence
such as benchmark results.
-->

# Are there any user-facing changes?
no
<!--
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.
-->

---------

Co-authored-by: rich-T-kid <richardbaah@MacBook-Air-de-Richard.local>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

arrow Changes to the arrow crate arrow-array development-process Related to development process of arrow-rs

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants