Why is `0.0 / 0.0` preferred over using NaN

### Description

Encountered an error when compiling native add-ons with MSVC.

Why do we prefer returning `0.0 / 0.0` instead of `NAN` from ``?

Example:

https://github.com/stdlib-js/stdlib/blob/a1f8442b4ed11aceb97c2b5e6e7e8fdc18d8317b/lib/node_modules/%40stdlib/stats/base/dists/negative-binomial/skewness/src/main.c#L42

### Related Issues

_No response_

### Questions

No.

### Demo

_No response_

### Reproduction

```shell

```

### Expected Results

```shell

```

### Actual Results

```shell

```

### Version

_No response_

### Environments

Node.js

### Browser Version

_No response_

### Node.js / npm Version

_No response_

### Platform

_No response_

### Checklist

- [x] Read and understood the [Code of Conduct](https://github.com/stdlib-js/stdlib/blob/develop/CODE_OF_CONDUCT.md).
- [x] Searched for existing issues and pull requests.

Start with the cited lib/node_modules/@stdlib/stats/base/dists/negative-binomial/skewness/src/main.c line and inspect how native add-ons are compiled with MSVC. Search the repository for similar uses of 0.0 / 0.0 and NAN, then reproduce the reported compilation issue; done means the portability rationale and any required follow-up are documented.

由索引模型根据 Issue 内容生成。