feat: add C APIs for half-precision floating-point number utilities

[gururaj1512]

---

type: pre_commit_static_analysis_report
description: Results of running static analysis checks when committing changes. report:

• task: lint_filenames status: passed
• task: lint_editorconfig status: passed
• task: lint_markdown status: passed
• task: lint_package_json status: passed
• task: lint_repl_help status: na
• task: lint_javascript_src status: passed
• task: lint_javascript_cli status: na
• task: lint_javascript_examples status: passed
• task: lint_javascript_tests status: passed
• task: lint_javascript_benchmarks status: na
• task: lint_python status: na
• task: lint_r status: na
• task: lint_c_src status: na
• task: lint_c_examples status: na
• task: lint_c_benchmarks status: na
• task: lint_c_tests_fixtures status: na
• task: lint_shell status: na
• task: lint_typescript_declarations status: passed
• task: lint_typescript_tests status: passed
• task: lint_license_headers status: passed ---

Resolves None

Description

What is the purpose of this pull request?

This pull request:

• feat: add C APIs for half-precision floating-point number utilities

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	$\color{green}107/107$ $\color{green}+100.00%$	$\color{green}3/3$ $\color{green}+100.00%$	$\color{green}0/0$ $\color{green}+100.00%$	$\color{green}107/107$ $\color{green}+100.00%$

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

[kgryte]

In general, you added far too many files what what was needed. Namely, a means to expose C APIs.

It is fine to add namespace files, but you took the direction of napi too literally. This namespace should be a mash-up of number/float64 with a couple of additional files (namely, include/* and manifest.json.

[kgryte]

In general, you added far too many files what what was needed. Namely, a means to expose C APIs.

It is fine to add namespace files, but you took the direction of napi too literally. This namespace should be a mash-up of number/float64 with a couple of additional files (namely, include/* and manifest.json.

[gururaj1512]

In general, you added far too many files what what was needed. Namely, a means to expose C APIs.

It is fine to add namespace files, but you took the direction of napi too literally. This namespace should be a mash-up of number/float64 with a couple of additional files (namely, include/* and manifest.json.

Got it...

[gururaj1512]

Needs @stdlib/number/float16/reviver and @stdlib/number/float16/to-json to be created and merged to land...