Closed kgryte closed 4 weeks ago
@kgryte Hey I would love to solve this issue
I'd like to work on this issue
@kgryte can you assign this issue to me?
This issue has been labeled as a good first issue and is available for anyone to work on.
If this is your first time contributing to an open source project, some aspects of the development process may seem unusual, arcane, or some combination of both.
Before working on this issue and opening a pull request, please read the project's contributing guidelines. These guidelines and the associated development guide provide important information, including links to stdlib's Code of Conduct, license policy, and steps for setting up your local development environment.
To reiterate, we strongly encourage you to refer to our contributing guides before beginning work on this issue. Failure to follow our guidelines significantly decreases the likelihood that you'll successfully contribute to stdlib and may result in automatic closure of a pull request without review.
Setting up your local development environment is a critical first step, as doing so ensures that automated development processes for linting, license verification, and unit testing can run prior to authoring commits and pushing changes. If you would prefer to avoid manual setup, we provide pre-configured development containers for use locally or in GitHub Codespaces.
We place a high value on consistency throughout the stdlib codebase. We encourage you to closely examine other packages in stdlib and attempt to emulate the practices and conventions found therein.
In short, the more effort you put in to ensure that your contribution looks and feels like stdlib—including variables names, bracket spacing, line breaks, etc—the more likely that your contribution will be reviewed and ultimately accepted. We encourage you to closely study the codebase before beginning work on this issue.
:sparkles: Thank you again for your interest in stdlib, and we look forward to reviewing your future contriubtions. :sparkles:
Description
This RFC proposes adding the package
@stdlib/array/base/cunone-by-right
, which cumulatively tests whether no array element in a provided array passes a test implemented by a predicate function, while iterating from right-to-left. The function should return a new generic array. The package should also provide an#assign
API for setting output values in a provided output array.where the
assign
API supports an offset and stride (see, e.g.,@stdlib/array/base/take
). Note that, by iterating from right to left, the values in the output array are equivalent to having first reversed the input arrayx
and then using left-to-right iteration.Both APIs should support accessor arrays (see, e.g.,
@stdlib/array/base/take
).Related Issues
No.
Questions
No.
Other
@stdlib/array/base/none-by-right
Checklist
RFC:
.