Repository navigation
docs: use dedicated zero-dimensional tensor constructor in blas/ext/base/ndarray/cxsa - #16685
Merged
Merged
Conversation
…base/ndarray/cxsa`
Contributor
Coverage Report
The above coverage report was generated for the changes in this PR. |
This was referenced Nov 18, 2026
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Resolves a part of #16654.
Description
This pull request:
@stdlib/blas/ext/base/ndarray/cxsato use the dedicatedComplex64Tensor0Dconstructor (@stdlib/ndarray/tensor0d/complex64) instead of@stdlib/ndarray/from-scalarwhen creating the zero-dimensionalalphandarray. The change covers the README examples, REPL text, TypeScript declaration example and type tests (docs/types/test.ts), JSDoc examples (lib/index.js,lib/main.js,lib/native.js),examples/index.js, the benchmarks, and the unit tests.Runtime code and TypeScript signatures are unchanged. The only edits under
lib/are@examplecomments.Related Issues
This pull request has the following related issues:
Reference Packages
This pull request followed these packages:
blas/ext/base/ndarray/daxpby(commit 3757981, referenced in the issue)blas/ext/base/ndarray/caxpby(for theComplex64Tensor0Dpattern)blas/ext/base/ndarray/cunitspace(docs: use dedicated zero-dimensional tensor constructor inblas/ext/base/ndarray/cunitspace#16675, including the review feedback)from-scalarplus the{ 'dtype': ... }options object with the typedtensor0dconstructor.var x = ...andvar alpha = ...in the documentation examples, as requested in the review of docs: use dedicated zero-dimensional tensor constructor inblas/ext/base/ndarray/cunitspace#16675.complex64takes the real and imaginary parts directly (new Complex64Tensor0D( 5.0, 0.0 )), so the intermediateComplex64instance and itsrequirewere removed.cunitspace, this package also has native variants (lib/native.js,test/test.native.js,benchmark/benchmark.native.js), which were updated in the same way.examples/index.js, because other statements sit betweenxandalphathere.Questions
No.
Other
Run locally for this package:
examples/index.jstest/test.js(4/4 pass),test/test.main.js(12/12 pass)test/test.native.js(12/12 pass), after building the addon withnode-gypbenchmark/benchmark.js(18/18 pass)benchmark/benchmark.native.js(18/18 pass)make lint-javascript-fileson the changed JavaScript files (no issues)make lint-markdown-fileson the README (no issues)make lint-typescript-declarations-filesondocs/types/index.d.tsanddocs/types/test.ts(no issues)@stdlib/_tools/lint/repl-txt) on the package'sdocs/repl.txt(no errors or warnings)Checklist
AI Assistance
If you answered "yes" above, how did you use AI assistance?
Disclosure
N/A. No AI assistance was used.
@stdlib-js/reviewers