feat: add lapack/base/dlaruv

[iampratik13]

---

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_pkg_readmes status: passed
• task: lint_markdown_docs status: na
• task: lint_markdown status: na
• 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 none.

Description

What is the purpose of this pull request?

This pull request:

• feat: add lapack/base/dlaruv

Related Issues

Does this pull request have any related issues?

This pull request has the following 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.

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

{{TODO: add disclosure if applicable}}

---

@stdlib-js/reviewers

[stdlib-bot]

Coverage Report

Package	Statements	Branches	Functions	Lines
lapack/base/dlaruv	$\\color{green}438/438$ $\\color{green}+0.00\\%$	$\\color{green}12/12$ $\\color{green}+0.00\\%$	$\\color{green}2/2$ $\\color{green}+0.00\\%$	$\\color{green}438/438$ $\\color{green}+0.00\\%$

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

[iampratik13]

https://github.com/stdlib-js/stdlib/tree/develop/lib/node_modules/%40stdlib/lapack/base/dpttrf

[kgryte]

Left initial comments.

[anandkaranubc]

@iampratik13 I updated the PR with some changes, based on the recent review. Can you please check those and confirm if everything looks good?

[iampratik13]

@anandkaranubc Yes, it looks good to me. Thanks for the improvements!

[kgryte]

This looks good. Only thing left is adding a reference citation which I will do later this evening after I add to the project's citation database.

[kgryte]

I think it is likely fine to have this be an Int32Array, especially given the range of desired seed values. There is some mild concern that this should be the same as CBLAS_INT (which could be either int64 or int32 depending). We can revisit once we add the C implementation.