bench: refactor to use string interpolation in ndarray/base

[anandkaranubc]

Progresses #8647
Progresses stdlib-js/metr-issue-tracker#403

Description

What is the purpose of this pull request?

This pull request:

• refactors to use string interpolation in @stdlib/ndarray/base

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
• [RFC]: use string interpolation in JavaScript benchmarks for @stdlib/ndarray metr-issue-tracker#403

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.

No.

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.".

Used a Cursor driven Skill+Workflow to achieve this migration with manual and automated sanity checks.

---

@stdlib-js/reviewers

[stdlib-bot]

Coverage Report

Package	Statements	Branches	Functions	Lines
ndarray/base/strides	$\color{green}116/116$ $\color{green}+0.00%$	$\color{green}11/11$ $\color{green}+0.00%$	$\color{green}1/1$ $\color{green}+0.00%$	$\color{green}116/116$ $\color{green}+0.00%$
ndarray/base/strides2order	$\color{green}137/137$ $\color{green}+0.00%$	$\color{green}19/19$ $\color{green}+0.00%$	$\color{green}1/1$ $\color{green}+0.00%$	$\color{green}137/137$ $\color{green}+0.00%$
ndarray/base/sub2ind	$\color{green}242/242$ $\color{green}+0.00%$	$\color{green}25/25$ $\color{green}+0.00%$	$\color{green}1/1$ $\color{green}+0.00%$	$\color{green}242/242$ $\color{green}+0.00%$
ndarray/base/to-array	$\color{green}174/174$ $\color{green}+0.00%$	$\color{green}14/14$ $\color{green}+0.00%$	$\color{green}2/2$ $\color{green}+0.00%$	$\color{green}174/174$ $\color{green}+0.00%$
ndarray/base/to-flippedlr	$\color{green}139/139$ $\color{green}+0.00%$	$\color{green}5/5$ $\color{green}+0.00%$	$\color{green}1/1$ $\color{green}+0.00%$	$\color{green}139/139$ $\color{green}+0.00%$
ndarray/base/to-flippedud	$\color{green}136/136$ $\color{green}+0.00%$	$\color{green}6/6$ $\color{green}+0.00%$	$\color{green}1/1$ $\color{green}+0.00%$	$\color{green}136/136$ $\color{green}+0.00%$
ndarray/base/to-reversed-dimension	$\color{green}145/145$ $\color{green}+0.00%$	$\color{green}3/3$ $\color{green}+0.00%$	$\color{green}1/1$ $\color{green}+0.00%$	$\color{green}145/145$ $\color{green}+0.00%$
ndarray/base/unary	$\color{green}10506/10506$ $\color{green}+0.00%$	$\color{green}690/690$ $\color{green}+0.00%$	$\color{green}43/43$ $\color{green}+0.00%$	$\color{green}10506/10506$ $\color{green}+0.00%$

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

[anandkaranubc]

@kgryte Before I try to fix the lint error here, could I please confirm if the right way to do it is:

For the non-blocked unaryNd benchmarks, should I change unary( x, y, identity ); to unary( x, y, order === 'row-major', identity ); everywhere?

[kgryte]

@anandkaranubc Yes, please!

I have in my local notes the following todo items:

- ndarray/base/unary
  - benchmarks are broken due to `isRowMajor` argument
- ndarray/base/unary-by
  - benchmarks are broken due to `isRowMajor` argument

[anandkaranubc]

@anandkaranubc Yes, please!

I have in my local notes the following todo items:

- ndarray/base/unary
  - benchmarks are broken due to `isRowMajor` argument
- ndarray/base/unary-by
  - benchmarks are broken due to `isRowMajor` argument

Thanks! Should be done now.

[kgryte]

@anandkaranubc Would you mind resolving the merge conflicts? 😬

[anandkaranubc]

@kgryte

Are we also updating patterns like these to

bench( format( '%s::base:ndims=2', pkg ), ... )?

[kgryte]

Yes, ideally. Some descriptions should use parameterization, rather than namespacing. This is an example of such a case.

This is where having plot support would be useful, as such patterns would be more evident based on visualization faceting. Sigh.

[kgryte]

LGTM. Any further modifications can be addressed in follow-up PRs.