Athan
One other addendum is that, rather than `mannwhitneyu`, we'd probably name `mann-whitney-u` for readability (e.g., `dmann-whitney-u`, `smann-whitney-u`, etc, with alias `dmannWhitneyU`, `smannWhitneyU`, `mannWhitneyU`, etc).
@ashutoshsao For this particular package, you need to keep the import statements. The package can be updated, but as you guessed in your question, you need to keep those statements...
@Amansingh0807 @prajjwalbajpai The provided advice above is not correct. You should not be manually running `npm install` in the root project folder. As documented in the development guide, you need...
As the CI failure is expected (at least for now; hopefully this is addressed soon(ish)), I'll go ahead and merge.
@kunal-511 Yes, this issue is still open.
This PR contains artifacts from an improper Git merge. As such, I'll go ahead and close. Feel free to submit another PR which cleanly implements the changes.
@gautam-krishna-sharma What you describe is essentially what I wrote in the OP. The only thing I will add is that whether you use ` => [ ... ]` or `returns...
Also, for this PR to move forward, CI should be passing. Currently, CI is failing on linting, benchmarks, examples, and tests.
I see that doctesting is failing due to missing `Float16Array` support. Will take a look.
@gunjjoshi Yes, I'll try and take a look at `ndarray/base/unary` tonight.