feat: add ndarray/base/ternary

[headlessNode]

---

type: pre_commit_static_analysis_report
description: Results of running static analysis checks when committing changes. report:

• task: lint_filenames status: passed
• task: lint_editorconfig status: passed
• task: lint_markdown status: passed
• task: lint_package_json status: passed
• task: lint_repl_help status: passed
• task: lint_javascript_src status: passed
• task: lint_javascript_cli status: na
• task: lint_javascript_examples status: passed
• task: lint_javascript_tests status: passed
• task: lint_javascript_benchmarks status: passed
• task: lint_python status: na
• task: lint_r status: na
• task: lint_c_src status: na
• task: lint_c_examples status: na
• task: lint_c_benchmarks status: na
• task: lint_c_tests_fixtures status: na
• task: lint_shell status: na
• task: lint_typescript_declarations status: passed
• task: lint_typescript_tests status: passed
• task: lint_license_headers status: passed ---

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

Description

What is the purpose of this pull request?

This pull request:

• add ndarray/base/ternary

Related Issues

Does this pull request have any related issues?

This pull request has the following related issues:

• Resolves [RFC]: add ndarray/base/ternary metr-issue-tracker#148

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 AI for most things but not as much as I would've liked to use it. Because having a lot files involved for various dimensional implementation the AI tends to increase work rather than decrease it. So, mostly used it for the main.js & index.js, tests, and docs.

---

@stdlib-js/reviewers

[stdlib-bot]

Coverage Report

Package	Statements	Branches	Functions	Lines
ndarray/base/ternary	$\color{red}6889/14534$ $\color{green}+0.11%$	$\color{red}123/124$ $\color{green}+0.00%$	$\color{red}10/44$ $\color{green}+0.00%$	$\color{red}6889/14534$ $\color{green}+0.11%$

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

[kgryte]

Currently reviewing this PR. First comment is that I am going to need to refactor every single blocked implementation, as all of the loops are currently incorrect.

I am not going to be able to finish tonight.

For METR, thus far,

review_time: 60 mins

[kgryte]

See 1eb2d62 for the types of changes that are necessary throughout all the loops in this PR.

TL;DR:

1. You needed to check the block loops against established practice. What you originally proposed moved various variable updates to an inner most loop. That should have been seen as problematic for obvious reasons.
2. Your variable ordering was erratic. Be consistent. If w is the last variable in the parameter list, it should also be the last variable in terms of declarations, updates, etc. Otherwise, you are just inviting inevitable chaos should you try and feed this to automation.

In general, automation is only as good as the clarity of thought preceding that automation.

[headlessNode]

@kgryte suggestions applied

[kgryte]

LGTM after some additional clean-up.

[kgryte]

For METR, additional review time

review_time: 38 mins