test: fix Complex64 import in tests

[Planeshifter]

Description

What is the purpose of this pull request?

This pull request:

• fixes an incorrect Complex64 import in two test files for @stdlib/strided/base/map-by2. Both test.main.js and test.ndarray.js required @stdlib/complex/float64/ctor (the Complex128 constructor) and assigned it to a variable named Complex64. The correct path is @stdlib/complex/float32/ctor. The fix is a one-line change on line 31 of each file, replacing float64 with float32 in the require path.

The wrong constructor was used exclusively as new Complex64( 0.0, 0.0 ). Because zero is exactly representable in both float32 and float64, no numerical assertion failed, masking the defect. The same root cause — a float64/float32 path substitution error — was identified and fixed today in the sibling package @stdlib/strided/base/binary (see commit 9a829b3 below). No source files, public APIs, or benchmarks are touched by this PR.

Related Issues

Does this pull request have any related issues?

None.

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.

Sibling precedent: 9a829b3 — identical defect patched in @stdlib/strided/base/binary, labeled "Bug" by maintainers.

Root cause: Copy-paste or code-generation error substituted float64 for float32 in the require path. Missed in original review because every instantiation is new Complex64( 0.0, 0.0 ), which satisfies float32 numeric comparisons regardless of which constructor is invoked.

Scope: 2 files changed, 2 lines changed (require paths only). No source files, no API surface, no benchmarks, no documentation affected. No regression is possible.

Reviewer verdicts (three independent agents, all approve, blocking: false):

• Correctness (Reviewer A/Opus): fix correctly addresses root cause; float64→float32 is the right change; no edge cases missed.
• Regression scope (Reviewer B/Opus): all Complex64 usages are ( 0.0, 0.0 ); change is strictly minimal; no regression possible.
• Style (Reviewer C/Sonnet): spacing, quotes, and module-path format match stdlib conventions and the sibling precedent exactly.

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

Claude Code identified the incorrect import path via a codebase-wide grep for the wrong float64/ctor binding, then applied the one-line fix in each file. Three separate Claude agent reviewers (correctness/Opus, regression-scope/Opus, style/Sonnet) independently verified the change before submission.

---

Generated by Claude Code

[stdlib-bot]

Coverage Report

Package	Statements	Branches	Functions	Lines
strided/base/map-by2	$\color{green}608/608$ $\color{green}+100.00%$	$\color{green}42/42$ $\color{green}+100.00%$	$\color{green}6/6$ $\color{green}+100.00%$	$\color{green}608/608$ $\color{green}+100.00%$

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

[kgryte]

/stdlib merge

[stdlib-bot]

Thank you for working on this pull request. However, we cannot accept your contribution as the issue this pull request seeks to resolve has already been addressed in a different pull request or commit.

Thank you again for your interest in stdlib, and we look forward to reviewing your future contributions.