feat: add constants/float16/gamma-lanczos-g

[Erennn7]

---

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 ---

Description

What is the purpose of this pull request?

This pull request:

• add constants/float16/gamma-lanczos-g

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/gamma-lanczos-g	$\color{green}48/48$ $\color{green}+100.00%$	$\color{green}1/1$ $\color{green}+100.00%$	$\color{green}0/0$ $\color{green}+100.00%$	$\color{green}48/48$ $\color{green}+100.00%$

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

[Amansingh0807]

Hi @Erennn7! 👋

Thanks for the PR. I just wanted to save you some time-I actually submitted a PR for this exact constant recently (#9022).

This constant (gamma-lanczos-g) isn't just a generic value; it depends entirely on the specific approximation algorithm used in the function implementation. Since stdlib doesn't have a half-precision Gamma implementation yet, @kgryte mentioned that this constant shouldn't be added in isolation.

You can see the detailed explanation from the maintainer here: Comment on PR #9022

Just thought I'd share so you don't put unnecessary effort into this!

[Erennn7]

@Amansingh0807 Thanks for the heads up! I appreciate you saving me the time. it makes sense not to add this constant without the corresponding Gamma implementation. I'll focus on the other float16 constants that don't have this dependency. Thanks again! 👍