bench: refactor to use logEachMap in examples

[Lokeshranjan8]

Resolves #none.

Description

What is the purpose of this pull request?

This pull request:

• {{TODO: add description describing what this pull request does}}

Related Issues

Does this pull request have any related issues?

This pull request has the following related issues:

• #{{TODO: add related issue number}}

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

{{TODO: add disclosure if applicable}}

---

@stdlib-js/reviewers

[stdlib-bot]

Coverage Report

Package	Statements	Branches	Functions	Lines
number/float32/base/add	$\color{green}177/177$ $\color{green}+0.00%$	$\color{green}5/5$ $\color{green}+0.00%$	$\color{green}2/2$ $\color{green}+0.00%$	$\color{green}177/177$ $\color{green}+0.00%$
number/float32/base/div	$\color{green}177/177$ $\color{green}+0.00%$	$\color{green}5/5$ $\color{green}+0.00%$	$\color{green}2/2$ $\color{green}+0.00%$	$\color{green}177/177$ $\color{green}+0.00%$
number/float32/base/identity	$\color{green}168/168$ $\color{green}+0.00%$	$\color{green}5/5$ $\color{green}+0.00%$	$\color{green}2/2$ $\color{green}+0.00%$	$\color{green}168/168$ $\color{green}+0.00%$
number/float32/base/mul	$\color{green}177/177$ $\color{green}+0.00%$	$\color{green}5/5$ $\color{green}+0.00%$	$\color{green}2/2$ $\color{green}+0.00%$	$\color{green}177/177$ $\color{green}+0.00%$
number/float32/base/sub	$\color{green}177/177$ $\color{green}+0.00%$	$\color{green}5/5$ $\color{green}+0.00%$	$\color{green}2/2$ $\color{green}+0.00%$	$\color{green}177/177$ $\color{green}+0.00%$
number/float64/base/div	$\color{green}172/172$ $\color{green}+0.00%$	$\color{green}5/5$ $\color{green}+0.00%$	$\color{green}2/2$ $\color{green}+0.00%$	$\color{green}172/172$ $\color{green}+0.00%$
number/float64/base/identity	$\color{green}168/168$ $\color{green}+0.00%$	$\color{green}5/5$ $\color{green}+0.00%$	$\color{green}2/2$ $\color{green}+0.00%$	$\color{green}168/168$ $\color{green}+0.00%$
number/float64/base/mul	$\color{green}172/172$ $\color{green}+0.00%$	$\color{green}5/5$ $\color{green}+0.00%$	$\color{green}2/2$ $\color{green}+0.00%$	$\color{green}172/172$ $\color{green}+0.00%$
number/float64/base/sub	$\color{green}172/172$ $\color{green}+0.00%$	$\color{green}5/5$ $\color{green}+0.00%$	$\color{green}2/2$ $\color{green}+0.00%$	$\color{green}172/172$ $\color{green}+0.00%$

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

[Lokeshranjan8]

If these changes look good, I’ll proceed with updating the README as well.

[Neerajpathak07]

@Lokeshranjan8 Please revert the changes for updated Copyright years.

[Neerajpathak07]

Also why are we not updating the markdown examples to use logEachMap mind updating those as well.
Take a look at how it is done in few merged PR's.
Re:- https://github.com/stdlib-js/stdlib/pull/9440/changes

[kgryte]

Thanks, @Lokeshranjan8, for doing this clean-up. If you could update the corresponding README examples, as suggested by Neeraj, that would be appreciated! Cheers!

[Lokeshranjan8]

@kgryte Sorry for the delay . I was busy with college work. updating it now.

[kgryte]

LGTM. Thanks, @Lokeshranjan8!

[Lokeshranjan8]

Can I create a good first issue for new contributors to apply the same change in other files as well? cc @kgryte

[kgryte]

@Lokeshranjan8 You don't need to be constantly merging develop into your branch after your PR has been approved. It is okay if it is a couple of commits behind by the time we click the merge button.

Before opening an issue, I suggest getting a sense for how widespread the changes need to be made across the code base. There may be particular namespaces we want to focus on, such as math/base/special and stats/base/dists, but we should confirm how many files actually need to be changed and whether we want to encourage newcomers to pitch in on the modernization effort.

[Lokeshranjan8]

Got it, I’ll take care of this next time.
I’ll do a proper check on how many files need refactoring and how suitable it is for new contributors, then discuss it with you on Zulip.