fix(lint): replace new Array() with sparse array literals in tests #9356

[surajgoraicse]

Resolves #9356>.

Description

What is the purpose of this pull request?

This pull request fixes JavaScript linting failures caused by the use of the new Array() constructor in test files.

This pull request:

• Replaces new Array(n) with array literals and explicit length assignment
• Preserves sparse array semantics required by the existing test cases
• Complies with the stdlib/no-new-array ESLint rule
• Does not introduce any functional or behavioral changes

Related Issues

Does this pull request have any related issues?

This pull request has the following related issues:

• Fix JavaScript lint errors #9356

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.

The change follows the recommended stdlib pattern for creating sparse arrays without using the new Array() constructor, ensuring lint compliance while maintaining test intent.

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.

I consulted ChatGPT to understand the stdlib/no-new-array linting rule and the recommended approach for preserving sparse array semantics. The code changes were written manually.

---

@stdlib-js/reviewers

[stdlib-bot]

👋 Hi there! 👋

And thank you for opening your first pull request! We will review it shortly. 🏃 💨

Getting Started

• Please read our contributing guidelines if you haven't already.
• For development guidance, refer to the development guide.

Next Steps

1. A project maintainer will approve GitHub Actions workflows for your PR.
2. All CI checks must pass before your submission can be fully reviewed.
3. You'll need to address any failures in linting or unit tests.

Running Tests Locally

You can use make to run any of the CI commands locally from the root directory of the stdlib repository:

# Run tests for all packages in the math namespace:
make test TESTS_FILTER=".*/@stdlib/math/.*"

# Run benchmarks for a specific package:
make benchmark BENCHMARKS_FILTER=".*/@stdlib/math/base/special/sin/.*"

If you haven't heard back from us within two weeks, please ping us by tagging the "reviewers" team in a comment on this PR.

If you have any further questions while waiting for a response, please join our Zulip community to chat with project maintainers and other community members.

We appreciate your contribution!

Documentation Links

• Contributing Guidelines
• Development Guide
• Zulip Chat
• make rules for running examples
• make rules for running unit tests
• make rules for running benchmarks