feat: add array/float16

[udaykakade25]

progresses #7347 and #7273

Description

What is the purpose of this pull request?

This pull request:

• Adds array/float16 folder

Related Issues

Does this pull request have any related issues?

This pull request:

• resolves feat: add assert/is-float16array #7273 feat: add assert/has-float16array-support #7347

Questions

Any questions for reviewers of this pull request?

No.

Other

Any other information relevant to this pull request? This may include screenshots, references, and/or implementation notes.

This is the third PR. First two PRs are interconnected to each other. In order to merge this PR, we need to first merge PR 1: #7273 and #7347

Checklist

Please ensure the following tasks are completed before submitting this pull request.

• Read, understood, and followed the contributing guidelines.

---

@stdlib-js/reviewers

[udaykakade25]

/stdlib update-copyright-years

[udaykakade25]

Hello @Planeshifter and @kgryte sir,
With this PR, i have completed array/float16.
Please do review and merge PR along with two previously mentioned PRs.

So, i can start working on adding float16 datatype support for array/base, array/*, strided/8 and ndarray/*

[kgryte]

@udaykakade25 Thank you for working on this. I left a few initial comments. The TL;DR is that the entire implementation needs to be reworked to be implemented in ES5. I strongly encourage you to emulate the style and approach used in array/bool and other custom array types implemented in stdlib.

[udaykakade25]

@udaykakade25 Thank you for working on this. I left a few initial comments. The TL;DR is that the entire implementation needs to be reworked to be implemented in ES5. I strongly encourage you to emulate the style and approach used in array/bool and other custom array types implemented in stdlib.

Hello @kgryte sir, I have refactored the whole polyfill.js file that follows stdlib style. Thanks for reviewing!!

[kgryte]

Also, for this PR to move forward, CI should be passing. Currently, CI is failing on linting, benchmarks, examples, and tests.

[udaykakade25]

Also, for this PR to move forward, CI should be passing. Currently, CI is failing on linting, benchmarks, examples, and tests.

Hello @kgryte sir,
I have changes that follow the standards below
TABS Indentation ✅
Alphabetical Order ✅
Offset >>> 0 fix ✅
Readonly added ✅
Error formatting ✅
Utilities Added ✅
No Anonymous functions ✅
Missing Statistics Added ✅

Regarding failed CI checks:
Just Linting errors in Readme.md and Repl.txt are remaining to fix.
Rest other issues are encountered because the assert\has-float16array-support #7347 and assert/is-float16array #7273 PRs is still pending.

[stdlib-bot]

@kgryte, available slash commands include:

• /stdlib check-files - Check for required files.
• /stdlib make-commands - Print make commands for package changed in PR.
• /stdlib update-copyright-years - Update copyright header years.
• /stdlib lint-autofix - Auto-fix lint errors.
• /stdlib merge - Merge changes from develop branch into this PR.
• /stdlib rebase - Rebase this PR on top of develop branch.

[kgryte]

Unfortunately, there were a number of things wrong with this PR, especially in the understanding of how the polyfill is intended to work. While array/bool and array/complex64 were intended to be examples of how to author the package, those packages are also purely userland array types; however, Float16Array is a built-in type which we are polyfilling, which means that we need to match its behavior exactly. We cannot simply make the polyfill an accessor array, while the builtin is not. This is thus requiring a lot of refactoring, which I am still doing.

So, while I would have liked to get this PR in, I'll likely need more time to do so.

[kgryte]

Okay. I think this PR is now ready provided CI passes for everything but the doctest return annotations, which will be resolved once this PR is merged.

I will check back later today, and, if everything looks good, I'll go ahead and merge.

[kgryte]

Checked. All CI failures are expected due to missing doctest support, which I will add in a follow-up commit. As such, I'll go ahead and merge this PR. Thanks, @udaykakade25 and @gururaj1512, for helping get this over the finish line!