Athan

@aayush0325 Looks like this PR still needs changes, as suggested above.

@Ankit-raj-11 Thank you for your interest. However, based on your comment above, you clearly did not read https://github.com/stdlib-js/stdlib/issues/8563#issuecomment-3560733734 which links to our contributing guidelines and development guide. I suggest you...

/stdlib merge

@0PrashantYadav0 Made some changes in https://github.com/stdlib-js/stdlib/pull/7100 that will likely need to be propagated to this and similar PRs of yours. Importantly, some of the changes I made in #7100 address...

The structure looks fine thus far.

@udaykakade25 Given https://github.com/stdlib-js/stdlib/pull/7435, should we close this PR? Seems like a duplicate of the work you are doing in the other PR.

@varshil-shah Thanks for raising this issue. I think the main concern I have with implementing sparse arrays is that, in order to perform computation efficiently, you need a sparse array...

This PR performs a change similar to https://github.com/stdlib-js/stdlib/pull/8564. If that PR doesn't move forward, this PR can serve as a fallback. Otherwise, once that PR is merged, this PR should...

@DivyanshuVortex Thanks for this PR. However, this is an instance where some up-front discussion could have been useful. While your implementation largely mirrors what can be found in `ttest` and...

@DivyanshuVortex I suggest studying the `stats/strided/*ztest` and `stats/strided/*ztest2` packages. One thing you'll find is https://github.com/stdlib-js/stdlib/tree/develop/lib/node_modules/%40stdlib/stats/base/ztest which provides a collection of helper packages which are used across the `ztest` strided packages....