feat: add number/float16/base/add

[Neerajpathak07]

Resolves none.

Description

What is the purpose of this pull request?

This pull request:

• Adds number/float16/base/add

Related Issues

Does this pull request have any related issues?

This pull request has the following related issues:

• none

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.

No.

Checklist

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

• Read, understood, and followed the contributing guidelines

AI Assistance

When authoring the changes proposed in this PR, did you use any kind of AI assistance?

• Yes
• No

If you answered "yes" above, how did you use AI assistance?

• Code generation (e.g., when writing an implementation or fixing a bug)
• Test/benchmark generation
• Documentation (including examples)
• Research and understanding

Disclosure

If you answered "yes" to using AI assistance, please provide a short disclosure indicating how you used AI assistance. This helps reviewers determine how much scrutiny to apply when reviewing your contribution. Example disclosures: "This PR was written primarily by Claude Code." or "I consulted ChatGPT to understand the codebase, but the proposed changes were fully authored manually by myself.".

{{TODO: add disclosure if applicable}}

---

@stdlib-js/reviewers

[stdlib-bot]

Coverage Report

Package	Statements	Branches	Functions	Lines
number/float16/base/add	$\color{green}177/177$ $\color{green}+0.00%$	$\color{green}5/5$ $\color{green}+0.00%$	$\color{green}2/2$ $\color{green}+0.00%$	$\color{green}177/177$ $\color{green}+0.00%$

The above coverage report was generated for the changes in this PR.

[Neerajpathak07]

/stdlib update-copyright-years

[Neerajpathak07]

@gururaj1512 Thanks for reviewing and flagging changes although I do have a few conflicting opinions on the description of examples!!

[kgryte]

This won't work the way you need it to. You need to compare against the bit sequence value for NaN. We do this in other benchmarks for float16.

[kgryte]

Better would be to use the eventual number/float16/base/assert/is-nan utility here.

[Neerajpathak07]

@kgryte Interesting, some of the upstream versions that I referred to such as number/float16/base/from-word, significand & to-float64. What I realized is that the JS implementation utilizes isnan() but commonly for the C benchmark we are adapting the antique if( out != out ) check.

Maybe this can we updated from here on, to utilize the nan check directly from the utilities we'll need add a C header for float16/base/assert/is-nan. If you green light this I'll get going.

[kgryte]

It depends on the package. The reason I recommended using the utility here is that float16 is special. So it is entirely a case-by-case basis. The TL;DR is that you need to think more deeply about what is being compared and whether it is applicable.

[Neerajpathak07]

Yeah, makes more sense!!!

[kgryte]

Left some initial comments.

[Neerajpathak07]

Will draft this PR for the time being till we add the macro and the utilities!!