fix: add parentheses to NaN macros

[anandkaranubc]

Resolves stdlib-js/metr-issue-tracker#1391

Description

What is the purpose of this pull request?

This pull request:

• Wraps STDLIB_CONSTANT_FLOAT64_NAN and STDLIB_CONSTANT_FLOAT32_NAN in parentheses so they always act as a single value. Without them, 1.0 / STDLIB_CONSTANT_FLOAT64_NAN expands to 1.0 / 0.0/0.0, which is inf instead of NaN.

Related Issues

Does this pull request have any related issues?

This pull request has the following related issues:

• Add parentheses to NaN macros in constants/float*/nan metr-issue-tracker#1391
• [RFC]: replace inline NaN generation with stdlib NaN constants in C source files (tracking issue) #11743
• refactor: use constants/float64/nan #11768

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.

I checked all current uses of both macros and none of them are affected, so this does not change any existing output. It just makes the macros safe to use inside larger expressions as #11743 moves more code over to them.

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

@stdlib-js/reviewers

[stdlib-bot]

Coverage Report

Package	Statements	Branches	Functions	Lines
constants/float32/nan	$\\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\\%$
constants/float64/nan	$\\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.

[kgryte]

Thanks for fixing, @anandkaranubc!