fix: add missing values in error messages in blas/base/sgemv

[ShabiShett07]

---

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: na
• task: lint_package_json status: na
• task: lint_repl_help status: na
• task: lint_javascript_src status: passed
• task: lint_javascript_cli status: na
• task: lint_javascript_examples status: na
• task: lint_javascript_tests status: passed
• task: lint_javascript_benchmarks status: na
• 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: na
• task: lint_typescript_tests status: na
• task: lint_license_headers status: passed ---

none

Description

What is the purpose of this pull request?

This pull request:

• This adds missing interpolated argument values in error messages.

Related Issues

Does this pull request have any related issues?

This pull request:

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

---

@stdlib-js/reviewers

[stdlib-bot]

Coverage Report

Package	Statements	Branches	Functions	Lines
blas/base/sgemv	$\color{green}460/460$ $\color{green}+100.00\%$	$\color{green}63/63$ $\color{green}+100.00\%$	$\color{green}3/3$ $\color{green}+100.00\%$	$\color{green}460/460$ $\color{green}+100.00\%$

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

[kgryte]

Left initial comments. As I mentioned elsewhere, we should not blindly add strideA* checks. This needs to be reasoned about on a per routine basis. For this and dgemv, I don't think the checks are warranted and they should be removed.

The fixed error messages, however, can stay.

[ShabiShett07]

@kgryte, now I got it the implementation needs to have LDA check for having stride checks. Now I am clear with it. Thank you!

[ShabiShett07]

@kgryte, ready for review