[RFC]: add `@stdlib/array/base/cuevery-by-right` about stdlib

[siddharthbaleja7]

I would like to solve this issue.Could you please assign this issue to me?

[kgryte]

@siddharthbaleja7 Thank you for volunteering to work on this. Please feel free to submit a PR implementing this feature.

[stdlib-bot]

🚨 Important: PLEASE READ 🚨

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.

1. You cannot "claim" issues. People new to open source often want to "claim" or be assigned an issue before beginning work. The typical rationale is that people want to avoid wasted work in the event that someone else ends up working the issue. However, this practice is not effective in open source, as it often leads to "issue squatting", in which an individual asks to be assigned, is granted their request, and then never ends up working on the issue. Accordingly, you are encouraged to communicate your intent to address this issue, ideally by providing a rough outline as to how you plan to address the issue or asking clarifying questions, but, at the end of the day, we will take running code and rough consensus in order to move forward quickly.
2. We have a very high bar for contributions. We have very high standards for contributions and expect all contributions—whether new features, tests, or documentation—to be rigorous, thorough, and complete. Once a pull request is merged into stdlib, that contribution immediately becomes the collective responsibility of all maintainers of stdlib. When we merge code into stdlib, we are saying that we, the maintainers, commit to reviewing subsequent changes and making bugfixes to the code. Hence, in order to ensure future maintainability, this naturally leads to a higher standard of contribution.

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.

• If you are attempting to contribute a new package, sometimes the best approach is to simply copy the contents of an existing package and then modify the minimum amount necessary to implement the feature (e.g., changing descriptions, parameter names, and implementation).
• If you are contributing tests, find a package implementing a similar feature and emulate the tests of that package.
• If you are updating documentation, examine several similar packages and emulate the content, style, and prose of those packages.

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.

✨ Thank you again for your interest in stdlib, and we look forward to reviewing your future contriubtions. ✨

[BarryByte]

@kgryte I'm interested in taking on the task of implementing the @stdlib/array/base/cuevery-by-right package. Here’s a brief outline of how I plan to approach it:

Understanding the Task: I’ll start by thoroughly reading the contributing guidelines, Code of Conduct, and license policy to ensure I'm aligned with the project's standards and practices.

Setting Up the Environment: I’ll set up my local development environment following the provided instructions. If necessary, I’ll use the pre-configured development containers to streamline the process.

Reviewing the Codebase: I’ll review similar packages like @stdlib/array/base/cuevery-by-right and @stdlib/array/base/take to understand the existing conventions and implementations.

Implementation Plan:

cueveryByRight Function: Implement the function to iterate from right-to-left, applying the predicate, and returning a new array with the results.
assign API: Extend the function to support assigning values to a provided output array, including handling offset and stride.
Accessor Arrays: Ensure both APIs support accessor arrays.
Testing and Documentation: I’ll write tests to cover various scenarios and document the package thoroughly to ensure it’s easy to use and understand.

I’ll make sure to follow all the contributing guidelines and submit a pull request that meets the project's standards. Looking forward to contributing!