feat: add constants/float16/nan

[GlyphicGuy]

---

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: passed
• 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 a part of #9061

Description

What is the purpose of this pull request?

This pull request:

• adds add constants/float16/nan

Related Issues

Does this pull request have any related issues?

This pull request has the following related issues:

• [RFC]: tracking issue for missing float16 constants #9061

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
constants/float16/nan	$color{green}48/48$ $color{green}+0.00%$	$color{green}1/1$ $color{green}+0.00%$	$color{green}0/0$ $color{green}+0.00%$	$color{green}48/48$ $color{green}+0.00%$

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

[DivyanshuVortex]

Hey @GlyphicGuy , I open a PR for this #9096

[GlyphicGuy]

Heyy @DivyanshuVortex , I think you have not referenced the #9061 in you PR, so I was not aware a about a PR open for the same thing. I see that you are already a contributor and I am trying to make my first contribution here, just wondering if this can be worked out?

[DivyanshuVortex]

You’re right — I didn’t reference the issue, my mistake. When I opened the PR, the issue hadn’t been approved by the maintainer therefore i didn't ref the issue , but the PR was already open.

[kgryte]

LGTM

[kgryte]

/stdlib update-copyright-years

[GlyphicGuy]

@kgryte Thank you so much for merging my PR. This counts as my first contribution to stdlib and I'm excited to learn and contribute better!