[hardikguptaofficialgit]

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/levy/stdev 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/levy/mode (refactor: use constants/float64/nan in stats/base/dists/levy/mode #16381)

What carried over from the reference(s)?

• include placement right after is_nan.h, the macro swap, and adding the dependency right after is-nan in each manifest entry

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

• this package already depends on constants/float64/pinf, so the new include and dependency sit between is-nan and pinf
• src/main.c is the only file with an inline NaN, so it is the only source change

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.

Built src/main.c with gcc -Wall -Wextra and no warnings. stdev( 0.0, 1.0 ) still returns Infinity, and c <= 0 or NaN inputs still return NaN.

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.

I used an AI assistant to make the edit following #16381, then checked the diff and compiled and ran the C implementation myself.

---

@stdlib-js/reviewers

[Copilot]

Copilot wasn't able to review any files in this pull request. Check if the Files changed in this pull request are included in default exclusions.

[stdlib-bot]

Coverage Report

Package	Statements	Branches	Functions	Lines
stats/base/dists/levy/stdev	$\\color{green}176/176$ $\\color{green}+100.00\\%$	$\\color{green}9/9$ $\\color{green}+100.00\\%$	$\\color{green}2/2$ $\\color{green}+100.00\\%$	$\\color{green}176/176$ $\\color{green}+100.00\\%$

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