Skip to content

Commit 229bafe

Browse files
committed
docs: update note
--- 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: na - task: lint_javascript_cli status: na - task: lint_javascript_examples status: na - task: lint_javascript_tests status: na - 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: passed - task: lint_typescript_tests status: na - task: lint_license_headers status: passed ---
1 parent 475dc22 commit 229bafe

File tree

1 file changed

+1
-1
lines changed
  • lib/node_modules/@stdlib/stats/cumax/docs/types

1 file changed

+1
-1
lines changed

lib/node_modules/@stdlib/stats/cumax/docs/types/index.d.ts

+1-1
Original file line numberDiff line numberDiff line change
@@ -77,7 +77,7 @@ interface Unary {
7777
* var arr = ndarray2array( y );
7878
* // returns [ -1.0, 2.0, 2.0 ]
7979
*/
80-
<T = unknown, U = unknown>( x: InputArray<T>, options?: Options ): OutputArray<U>; // NOTE: we lose type specificity here, but retaining specificity would likely be difficult and/or tedious to completely enumerate, as the output ndarray data type is dependent on how `x` interacts with output data type policy and whether that policy has been overridden by `options.dtype`. In principle, as well, based on the policy, it is possible to know more exactly which `InputArray` types are actually allowed.
80+
<T = unknown, U = unknown>( x: InputArray<T>, options?: Options ): OutputArray<U>; // NOTE: we lose type specificity here, but retaining specificity would likely be difficult and/or tedious to completely enumerate, as the output ndarray data type is dependent on how `x` interacts with output data type policy and whether that policy has been overridden by `options.dtype`.
8181

8282
/**
8383
* Computes the cumulative maximum value along one or more ndarray dimensions and assigns results to a provided output ndarray.

0 commit comments

Comments
 (0)