bench: refactor to use string interpolation in number/uint8/base/mul

[opbot-xd]

---

type: pre_commit_static_analysis_report
description: Results of running static analysis checks when committing changes.
report:

• task: lint_filenames
  status: passed
• task: lint_editorconfig
  status: passed
• task: lint_markdown
  status: na
• task: lint_package_json
  status: na
• task: lint_repl_help
  status: na
• task: lint_javascript_src
  status: na
• task: lint_javascript_cli
  status: na
• task: lint_javascript_examples
  status: na
• task: lint_javascript_tests
  status: na
• task: lint_javascript_benchmarks
  status: passed
• task: lint_python
  status: na
• task: lint_r
  status: na
• task: lint_c_src
  status: na
• task: lint_c_examples
  status: na
• task: lint_c_benchmarks
  status: na
• task: lint_c_tests_fixtures
  status: na
• task: lint_shell
  status: na
• task: lint_typescript_declarations
  status: passed
• task: lint_typescript_tests
  status: na
• task: lint_license_headers
  status: passed

---

Resolves a part of #8647.

Description

What is the purpose of this pull request?

This pull request:

• Refactors JavaScript benchmarks in @stdlib/number/uint8/base/mul to use @stdlib/string/format for string interpolation instead of string concatenation when specifying benchmark names.

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.

• Updated benchmark.js to replace pkg+'::inline' with format( '%s::inline', pkg )
• Updated benchmark.native.js to replace pkg+'::native' with format( '%s::native', pkg )
• All benchmarks run successfully and produce the same output as before
• No other changes were made to the benchmark logic

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

---

@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
number/uint8/base/mul	$\color{green}157/157$ $\color{green}+100.00%$	$\color{green}5/5$ $\color{green}+100.00%$	$\color{green}2/2$ $\color{green}+100.00%$	$\color{green}157/157$ $\color{green}+100.00%$

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

[kgryte]

LGTM