Fix stream view construction in new benchmark

[wence-]

Description

Adapt the new benchmark from #23889 to the stream_ref changes of #23770.

These two "conflicted" but not in a merge-conflict way.

Checklist

• I am familiar with the Contributing Guidelines.
• New or existing tests cover these changes.
• The documentation is up to date with these changes.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: 7c211578-7d20-4745-bffb-1572038c91aa

📥 Commits

Reviewing files that changed from the base of the PR and between ff325a4 and a66d867.

📒 Files selected for processing (1)

• cpp/benchmarks/dictionary/concatenate.cpp

Included review availability: Your plan provides up to 12 included reviews per hour; 11 remain after this review.

---

📝 Summary

Summary by CodeRabbit

• Bug Fixes
  • Updated the dictionary concatenation benchmark’s CUDA stream handling for compatibility with the current stream interface.

Walkthrough

The dictionary concatenate benchmark now passes its CUDA stream to nvbench through stream.get() instead of stream.value().

Changes

Dictionary benchmark

Layer / File(s)	Summary
Update benchmark stream configuration cpp/benchmarks/dictionary/concatenate.cpp	bench_dictionary_concatenate_indices now uses stream.get() when configuring nvbench.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Merge Risk: ⚪ Minimal · up to a66d8

This localized benchmark fix changes how the stream is passed during setup and introduces no actionable merge-blocking risk; it is merge-ready after normal checks and review.

Suggested reviewers: vyasr

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly identifies the main change: fixing stream view construction in the new benchmark.
Description check	✅ Passed	The description explains that the benchmark must align with the stream_ref changes and addresses the conflict between the prior changes.
Docstring Coverage	✅ Passed	Docstring coverage is 100.00% which is sufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 1 functions across 1 files.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

_{Comment @coderabbitai help to get the list of available commands.}

[davidwendt]

/merge