feat: add ndarray/base/rot180

[headlessNode]

Resolves stdlib-js/metr-issue-tracker#302.

Description

What is the purpose of this pull request?

This pull request:

• add ndarray/base/rot180

Related Issues

Does this pull request have any related issues?

This pull request has the following related issues:

• Resolves [RFC]: add ndarray/base/rot180 metr-issue-tracker#302

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

Primarily written by Claude Code.

---

@stdlib-js/reviewers

[stdlib-bot]

Coverage Report

Package	Statements	Branches	Functions	Lines
ndarray/base/rot180	$\color{green}96/96$ $\color{green}+0.00%$	$\color{green}3/3$ $\color{green}+0.00%$	$\color{green}1/1$ $\color{green}+0.00%$	$\color{green}96/96$ $\color{green}+0.00%$

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

[kgryte]

LGTM after a decent amount of clean-up.

[kgryte]

Also, please make sure you are following our contributing process. Some of the lint errors should have been caught by our Git hooks. That they made it to CI tells me that you skipped local dev env setup. Simply because there are TS errors does not mean that you should be skipping all of our commit hooks. You can disable them selectively when warranted. Examine the hook source to see how.

[kgryte]

As the CI failure is expected, I'll go ahead and merge.