[devxsubh]

Resolves None.

Description

What is the purpose of this pull request?

This pull request:

• replaces inline NaN generation in the C implementation of stats/base/dists/laplace/pdf with STDLIB_CONSTANT_FLOAT64_NAN
• adds @stdlib/constants/float64/nan to the build, benchmark, and examples manifest entries

Related Issues

Does this pull request have any related issues?

This pull request has the following related issues:

• [RFC]: replace inline NaN generation with stdlib NaN constants in C source files (tracking issue) #11743

Reference Packages

Did the content of this pull request follow one or more existing packages? Answering is optional.

This pull request followed these packages:

• stats/base/dists/laplace/stdev (refactor: use constants/float64/nan in stats/base/dists/laplace/stdev #16558)

What carried over from the reference(s)?

• include placement, macro usage, and manifest dependency updates

What differed, or what did you have to work out yourself?

• checked the benchmark, example, and README C snippets; none had inline NaN, so only src/main.c changed
• compiled src/main.c before and after the change (-O2 -Wall -Wextra): no warnings, and the generated machine code is identical, since the macro expands to ( 0.0 / 0.0 )

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

This PR was written primarily by Claude Code, which applied the refactor and verified it by compiling the old and new C source and comparing the generated machine code. I reviewed the diff before submitting.

---

@stdlib-js/reviewers

[stdlib-bot]

Hello! 👋

We've noticed that you've been opening a number of PRs addressing good first issues. Thank you for your interest and enthusiasm!

Now that you've made a few contributions, we suggest no longer working on good first issues. Instead, we encourage you to prioritize cleaning up any PRs which have yet to be merged and then proceed to work on more involved tasks.

Not only does this ensure that other new contributors can work on things and get ramped up on all things stdlib, it also ensures that you can spend your time on more challenging problems. 🚀

For ideas for future PRs, feel free to search the codebase for TODOs and FIXMEs and be sure to check out other open issues on the issue tracker. Cheers!

[stdlib-bot]

Coverage Report

Package	Statements	Branches	Functions	Lines
stats/base/dists/laplace/pdf	$\\color{green}292/292$ $\\color{green}+100.00\\%$	$\\color{green}19/19$ $\\color{green}+100.00\\%$	$\\color{green}4/4$ $\\color{green}+100.00\\%$	$\\color{green}292/292$ $\\color{green}+100.00\\%$

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