feat: add blas/base/wasm/zscal

[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: 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 ---

Progresses #2039

Description

What is the purpose of this pull request?

This pull request:

• Adds the package blas/base/wasm/zscal

Related Issues

Does this pull request have any related issues?

This pull request:

• progresses [RFC]: Add BLAS bindings and implementations for linear algebra (tracking issue) #2039

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

[ShabiShett07]

/stdlib update-copyright-years

[stdlib-bot]

Coverage Report

Package	Statements	Branches	Functions	Lines
blas/base/wasm/zscal	$\color{green}698/698$ $\color{green}+100.00\%$	$\color{green}17/17$ $\color{green}+100.00\%$	$\color{green}6/6$ $\color{green}+100.00\%$	$\color{green}698/698$ $\color{green}+100.00\%$
complex/float64/base/mul	$\color{green}310/310$ $\color{green}+100.00\%$	$\color{green}9/9$ $\color{green}+100.00\%$	$\color{green}4/4$ $\color{green}+100.00\%$	$\color{green}310/310$ $\color{green}+100.00\%$

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

[ShabiShett07]

@kgryte, I have changed the variable names

[kgryte]

You seem to be a bit confused regarding bytes offsets and the mixing of real and complex.

Suggested change

	mod.realloc( ((N*2)*nb)+nb );
	// Define a pointer (i.e., byte offset) to the first vector element:
	xptr = 0;
	// Define a pointer to a complex number:
	zptr = (N*2) * nb;
	// Write random values to module memory:
	mod.write( xptr, uniform( (N*2), -100.0, 100.0, options ) );
	mod.write( zptr, new Float64Array( [ 1.0, 0.0 ] ) );
	// Retrieve a DataView of module memory:
	view = mod.view;
	b.tic();
	for ( i = 0; i < b.iterations; i++ ) {
	mod.main( (N*2), zptr, xptr, 1 );
	byteOffset = xptr + ( (i%(N*2))*nb );
	mod.realloc( (N*nb)+nb );
	// Define a pointer (i.e., byte offset) to the first vector element:
	xptr = 0;
	// Define a pointer to a complex number:
	zptr = N * nb;
	// Write random values to module memory:
	mod.write( xptr, uniform( (N*2), -100.0, 100.0, options ) );
	mod.write( zptr, new Float64Array( [ 1.0, 0.0 ] ) );
	// Retrieve a DataView of module memory:
	view = mod.view;
	b.tic();
	for ( i = 0; i < b.iterations; i++ ) {
	mod.main( N, zptr, xptr, 1 );
	byteOffset = xptr + ( (i%N)*nb );

[kgryte]

Same changes here. You are over-allocating by 2x. nb is the number of bytes per element for complex128, not float64.

[kgryte]

Suggested change

	// Advanced indexing:
	// Using `N` and stride parameters:

[kgryte]

Suggested change

	> var alpha = new {{alias:@stdlib/complex/float64/ctor}}( 2.0, 2.0 );
	> alpha = new {{alias:@stdlib/complex/float64/ctor}}( 2.0, 2.0 );

alpha has already been declared above.

[kgryte]

Suggested change

	Complex constant.
	Scalar constant.

[kgryte]

Suggested change

	Complex constant.
	Scalar constant.

[kgryte]

Suggested change

	Pointer (i.e., byte offset) to a scalar complex constant.
	Pointer (i.e., byte offset) to a scalar constant.

[kgryte]

Suggested change

	Pointer (i.e., byte offset) to a scalar complex constant.
	Pointer (i.e., byte offset) to a scalar constant.

[kgryte]

This test is incorrect. You need to actually confirm that the original array is unchanged. This test does nothing of the sort. For an idea of what is expected, see blas/base/wasm/daxpy/test/test.module.main.js.

[kgryte]

It doesn't return a reference. It returns a pointer. See the Wasm implementation for daxpy.

[kgryte]

It doesn't return a reference. It returns a pointer. See the Wasm implementation for daxpy.

[kgryte]

Same comment. You are not testing that the array is left unchanged.

[kgryte]

Left initial comments. This PR is mostly in good shape. The most glaring defect is in the tests.