feat: add lapack/base/dlange

[aayush0325]

Description

What is the purpose of this pull request?

This pull request:

• adds lapack/base/dlange

Related Issues

Does this pull request have any related issues?

No.

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
lapack/base/dlange	$\color{green}683/683$ $\color{green}+100.00\%$	$\color{red}51/55$ $\color{green}+92.73\%$	$\color{green}7/7$ $\color{green}+100.00\%$	$\color{green}683/683$ $\color{green}+100.00\%$

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

[kgryte]

@aayush0325 I think you need to update the label for this and the other equations. Each label should be unique. This appears to be a copy-paste mistake.

[kgryte]

Suggested change

	- **norm**: specifies the type of norm to be calculated, should be one of the following: `max`, `one`, `frobenius` or `infinity`.
	- **norm**: specifies the type of norm to be calculated, should be one of the following: `max`, `one`, `frobenius`, or `infinity`.

Oxford comma.

[kgryte]

Suggested change

	- **work**: [`Float64Array`][mdn-float64array] used as a temporary workspace.
	`work` should have `N` indexed elements if calculating the one norm in a row-major layout and `M` indexed elements if calculating the infinity norm in column-major layout, in all other cases it is fine to pass a dummy [`Float64Array`][mdn-float64array].
	- **work**: [`Float64Array`][mdn-float64array] used as a temporary workspace. When `A` is row-major and `norm` is `one`, `work` should have at least `N` indexed elements. When `A` is column-major` and `norm` is `infinity`, work` should have at least `M` indexed elements. In all other cases, `work` is not used and can have any number of elements, including zero.

[kgryte]

Same changes as above.

[kgryte]

Suggested change

	* @returns {number} required norm value
	* @returns {number} result

"required" norm value is an odd description. Fine to just use result here and below.

[kgryte]

This can be moved to the parent scope as a workspace which can be reused below. This avoids repeated allocation.

[kgryte]

Suggested change

	if ( norm === 'max' ) {
	return maxAbs( M, N, A, strideA1, strideA2, offsetA );
	}
	if ( norm === 'one' ) {
	return oneNorm( M, N, A, strideA1, strideA2, offsetA, work, strideWork, offsetWork ); // eslint-disable-line max-len
	}
	if ( norm === 'infinity' ) {
	return infinityNorm( M, N, A, strideA1, strideA2, offsetA, work, strideWork, offsetWork ); // eslint-disable-line max-len
	}
	if ( norm === 'max' ) {
	return maxAbs( M, N, A, strideA1, strideA2, offsetA );
	}
	if ( norm === 'one' ) {
	return oneNorm( M, N, A, strideA1, strideA2, offsetA, work, strideWork, offsetWork ); // eslint-disable-line max-len
	}
	if ( norm === 'infinity' ) {
	return infinityNorm( M, N, A, strideA1, strideA2, offsetA, work, strideWork, offsetWork ); // eslint-disable-line max-len
	}

[kgryte]

No need for an object. Just include the array in this file. Having a nested object just waste characters and space.

[kgryte]

Suggested change

	// VARIABLES //

[kgryte]

Suggested change

	* @name isOperation
	* @private
	* @name isOperation

This function should be considered a private internal function relative to the package. It is not for public consumption.

[kgryte]

Mind renaming this file to is_operation.js to be consistent with elsewhere and the isOperation convention?

[kgryte]

We typically use loopOrder when implementing a blocked algorithm. Instead, I suggest doing something similar to L281 below and use an explicit if statement.

[kgryte]

Left initial comments.