test: add special value tests for log1pmx

[ashish-066]

---

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: na
• task: lint_package_json
  status: na
• task: lint_repl_help
  status: na
• task: lint_javascript_src
  status: na
• task: lint_javascript_cli
  status: na
• task: lint_javascript_examples
  status: na
• 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: na
• task: lint_license_headers
  status: passed

---

Resolves N/A.

Description

This pull request:

• Adds explicit tests for NaN, ±Infinity, and negative zero handling in log1pmx.

Related Issues

This pull request has no related issues.

Questions

No.

Other

No.

Checklist

• Read, understood, and followed the contributing guidelines.

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

I consulted AI to understand the stdlib testing conventions and to identify missing edge cases. The test changes themselves were authored and validated manually.

---

@stdlib-js/reviewers

[stdlib-bot]

👋 Hi there! 👋

And thank you for opening your first pull request! We will review it shortly. 🏃 💨

Getting Started

• Please read our contributing guidelines if you haven't already.
• For development guidance, refer to the development guide.

Next Steps

1. A project maintainer will approve GitHub Actions workflows for your PR.
2. All CI checks must pass before your submission can be fully reviewed.
3. You'll need to address any failures in linting or unit tests.

Running Tests Locally

You can use make to run any of the CI commands locally from the root directory of the stdlib repository:

# Run tests for all packages in the math namespace:
make test TESTS_FILTER=".*/@stdlib/math/.*"

# Run benchmarks for a specific package:
make benchmark BENCHMARKS_FILTER=".*/@stdlib/math/base/special/sin/.*"

If you haven't heard back from us within two weeks, please ping us by tagging the "reviewers" team in a comment on this PR.

If you have any further questions while waiting for a response, please join our Zulip community to chat with project maintainers and other community members.

We appreciate your contribution!

Documentation Links

• Contributing Guidelines
• Development Guide
• Zulip Chat
• make rules for running examples
• make rules for running unit tests
• make rules for running benchmarks

[kgryte]

Why does this make sense?

[ashish-066]

the current implementation already preserves -0. The purpose of this test is to explicitly specify

[kgryte]

And I am asking you to think more critically about whether that makes sense.

In general, we should not be adding tests for the sake of adding tests. Adding tests such as those you have added here document the desired public contract with downstream consumers. We should ensure that the contract makes sense mathematically. It is possible that the implementation is incorrect.

[ashish-066]

Sorry for the misunderstanding. You are right there is no mathematical necessity to specify signed zero behavior for log1pmx.I have removed the -0 test case