feat: add blas/ext/base/dindex-of-row

[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: missing_dependencies
• task: lint_c_examples status: missing_dependencies
• task: lint_c_benchmarks status: missing_dependencies
• 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#219.

Description

What is the purpose of this pull request?

This pull request:

• add blas/ext/base/dindex-of-row

Related Issues

Does this pull request have any related issues?

This pull request has the following related issues:

• Resolves [RFC]: add blas/ext/base/dindex-of-row metr-issue-tracker#219

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
blas/ext/base/dindex-of-row	$\color{green}531/531$ $\color{green}+0.00%$	$\color{green}52/52$ $\color{green}+0.00%$	$\color{green}4/4$ $\color{green}+0.00%$	$\color{green}531/531$ $\color{green}+0.00%$

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

[kgryte]

Left initial comments.

[kgryte]

For METR,

review_time: 45 mins

[kgryte]

I will note that, in

stdlib/lib/node_modules/@stdlib/blas/base/dger/src/dger.c

Line 38 in eec976a

void API_SUFFIX(c_dger)( const CBLAS_LAYOUT layout, const CBLAS_INT M, const CBLAS_INT N, const double alpha, const double *X, const CBLAS_INT strideX, const double *Y, const CBLAS_INT strideY, double *A, const CBLAS_INT LDA ) {

, we performed input argument validation, similar to JavaScript. Validation logic was included to ensure we matched CBLAS.

Similarly, we performed validation in the ndarray interface, as well.

I am okay with leaving both out for now, despite it meaning that our C and JS implementations diverge in their error handling behavior and for our extended BLAS interfaces diverging a bit from our reference BLAS implementations.

[kgryte]

LGTM

[kgryte]

For METR,

review_time: 25 mins