Athan
> How will this benefit users and developers? This is already addressed in the OP. Second paragraph.
@SarthakPaandey Before you begin, it would be best to communicate what you're planning to work on. Some of the above routines are easier than others and should be addressed first....
@headlessNode That makes sense. I am currently working on `for-each`, which is related.
@headlessNode I suggest working a "base" implementation of `map` first. For `@stdlib/ndarray/base/map`, we can assume that an output array is provided, similar to `ndarray/base/unary`. In fact, `unary` is a good...
@headlessNode Yes. As an example, see https://github.com/stdlib-js/stdlib/tree/develop/lib/node_modules/%40stdlib/array/base/any-by.
@headlessNode Pushed up a POC implementation of `for-each`: https://github.com/stdlib-js/stdlib/tree/develop/lib/node_modules/%40stdlib/ndarray/base/for-each
Sounds good, @headlessNode! Thanks for the heads up!
@headlessNode Do you currently have anything in progress? @DhruvArvindSingh If this is your first time contributing to stdlib, you may want to first knock out a few "Good First Issues"...
@gururaj1512 If you are interested in working on this, I suggest the two lowest hanging fruit are `fill` and `with`, as they can wrap `base/assign`, which is already implemented. We...
@gururaj1512 And I suggest prioritizing `with` first, as `fill` will require optional slice support (e.g., `fill( x, value[, MultiSlice])`).