Repository navigation
feat: add blas/ext/base/dwxmy - #13688
Conversation
---
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: passed
- task: lint_c_examples
status: passed
- task: lint_c_benchmarks
status: passed
- 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
---
|
|
||
| # dwxmy | ||
|
|
||
| > Perform the element-wise operation `w = x * y` for double-precision floating-point strided arrays. |
There was a problem hiding this comment.
Finally taking a step toward less verbose descriptions :)
There was a problem hiding this comment.
Yes, although, I am not sure we want to go that direction given your existing precedent for gwxmy and the rest of the *wx*y family of packages. Meaning, if we are going to go concise, it should be consistent across them all.
Given that the more verbose description is already in use for gwxmy, I am thinking we should also be more verbose here.
There was a problem hiding this comment.
@anandkaranubc Also see #13688 (comment). Your call. I am fine either way.
Coverage Report
The above coverage report was generated for the changes in this PR. |
| */ | ||
| interface Routine { | ||
| /** | ||
| * Performs the element-wise operation `w = x * y` for double-precision floating-point strided arrays. |
There was a problem hiding this comment.
@anandkaranubc This is a different description than what you used in gwxmy. Shouldn't we be consistent here?
There was a problem hiding this comment.
Agreed, @kgryte. This description, however, was getting way too verbose. If this is fine, I will go ahead and change the gwxmy description too.
There was a problem hiding this comment.
Otherwise, we would have:
Multiplies elements of a double-precision floating-point strided array xby the corresponding elements of a double-precision floating-point strided arrayyand assigns the results to elements in a double-precision floating-point strided arrayw using alternative indexing semantics.
There was a problem hiding this comment.
Up to you. It isn't just gwxmy, but also gwxpy and gwxsy would need to be migrated.
kgryte
left a comment
There was a problem hiding this comment.
Main comment concerns the descriptions.
---
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: 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: passed
- task: lint_c_examples
status: passed
- 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 stdlib-js/metr-issue-tracker#1082
Description
This pull request:
blas/ext/base/dwxmyRelated Issues
This pull request has the following related issues:
blas/ext/base/dwxmymetr-issue-tracker#1082Questions
No.
Other
No.
Checklist
AI Assistance
If you answered "yes" above, how did you use AI assistance?
Disclosure
Used Cursor+VS Code code-generation tools to help assist with the feature.
@stdlib-js/reviewers