feat: add stats/array/range-by

[gururaj1512]

---

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

Resolves None

Description

What is the purpose of this pull request?

This pull request:

• feat: add stats/array/range-by

Related Issues

Does this pull request have any related issues?

This pull request:

• resolves None

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

[gururaj1512]

/stdlib merge

[stdlib-bot]

Coverage Report

Package	Statements	Branches	Functions	Lines
stats/array/range-by	$\color{green}124/124$ $\color{green}+100.00\%$	$\color{green}8/8$ $\color{green}+100.00\%$	$\color{green}2/2$ $\color{green}+100.00\%$	$\color{green}124/124$ $\color{green}+100.00\%$

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

[kgryte]

@gururaj1512 This isn't correct. Something is off here. The callback should be provided the input array. If this isn't true, then the upstream implementation is incorrect.

[kgryte]

If you encounter something like this, don't just update the test in order to get the test to pass. Be sure to reflect on what should be the case and consider the possibility that upstream implementations may be wrong. In this case, that was the case.

[kgryte]

/stdlib merge

[kgryte]

LGTM after clean-up.