bench: refactor to use string interpolation in array/base/bifurcate-entries-by

[Amansingh0807]

Resolves a part of #8647.

Description

What is the purpose of this pull request?

This pull request:

• Refactors the JavaScript benchmark in @stdlib/array/base/bifurcate-entries-by to use @stdlib/string/format for string interpolation instead of string concatenation when specifying the benchmark name

Related Issues

Does this pull request have any related issues?

This pull request has the following related issues:

• [RFC]: use string interpolation in JavaScript benchmarks for the benchmark name (tracking issue) #8647

Questions

Any questions for reviewers of this pull request?

No.

Other

Any other information relevant to this pull request? This may include screenshots, references, and/or implementation notes.

Changes made:

• Added @stdlib/string/format import to the MODULES section
• Replaced string concatenation pkg+':len='+len with format( '%s:len=%d', pkg, len )

Testing:
Ran the benchmark locally using node lib\node_modules\@stdlib\array\base\bifurcate-entries-by\benchmark\benchmark.length.js and verified that:

• The benchmark executes successfully without errors
• The formatted benchmark names match the original output exactly (@stdlib/array/base/bifurcate-entries-by:len=10, etc.)
• All 18 benchmark tests pass

Checklist

Please ensure the following tasks are completed before submitting this pull request.

• Read, understood, and followed the contributing guidelines.

AI Assistance

When authoring the changes proposed in this PR, did you use any kind of AI assistance?

• Yes
• No

If you answered "yes" above, how did you use AI assistance?

• Code generation (e.g., when writing an implementation or fixing a bug)
• Test/benchmark generation
• Documentation (including examples)
• Research and understanding

Disclosure

If you answered "yes" to using AI assistance, please provide a short disclosure indicating how you used AI assistance. This helps reviewers determine how much scrutiny to apply when reviewing your contribution. Example disclosures: "This PR was written primarily by Claude Code." or "I consulted ChatGPT to understand the codebase, but the proposed changes were fully authored manually by myself.".

---

@stdlib-js/reviewers

[stdlib-bot]

Hello! 👋

We've noticed that you've been opening a number of PRs addressing good first issues. Thank you for your interest and enthusiasm!

Now that you've made a few contributions, we suggest no longer working on good first issues. Instead, we encourage you to prioritize cleaning up any PRs which have yet to be merged and then proceed to work on more involved tasks.

Not only does this ensure that other new contributors can work on things and get ramped up on all things stdlib, it also ensures that you can spend your time on more challenging problems. 🚀

For ideas for future PRs, feel free to search the codebase for TODOs and FIXMEs and be sure to check out other open issues on the issue tracker. Cheers!

[stdlib-bot]

Coverage Report

Package	Statements	Branches	Functions	Lines
array/base/bifurcate-entries-by	$\color{green}123/123$ $color{green}+100.00%$	$\color{green}9/9$ $color{green}+100.00%$	$\color{green}1/1$ $color{green}+100.00%$	$\color{green}123/123$ $color{green}+100.00%$

The above coverage report was generated for the changes in this PR.

[kgryte]

LGTM

[Amansingh0807]

@kgryte Thank you for the guidance!
Since there are still hundreds of files left for the same benchmark update, I want to ask whether I should continue working on them or move on to more complex issues instead. I am comfortable with the codebase structure now and happy to work on whatever you recommend.