add Float::exp

[tonyfettes]

This PR adds Float::exp. The code is basically transcribed from the musl libc.

https://git.musl-libc.org/cgit/musl/tree/src/math/expf.c

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[peter-jerry-ye-code-review]

From the provided git diff output, here are three potential issues or areas of concern that I've identified:

1. Potential Typo in Documentation Update:

   • In the NOTICE file, the update mentions "File float/exp.mbt and float/log.mbt is adapted from musl". However, the diff only shows changes related to float/exp.mbt, not float/log.mbt. This could be a typo or an oversight where the intention was to update the documentation for both files but only the exp.mbt file was actually modified.

2. Incomplete Error Handling in exp Function:

   • In the exp function within float/exp.mbt, there are checks for specific values like infinity and neg_infinity, and special cases are handled. However, there is no explicit error handling or documentation about what happens if the input is NaN (Not-a-Number). While the function might implicitly handle NaN by returning NaN (as per IEEE 754 standards), it would be beneficial to explicitly mention this in the comments or include a check to make the handling more transparent.

3. Missing exp Function Definition in float.mbti:

   • The diff shows the addition of the exp function in the Float implementation within float/float.mbti. However, the function body is not shown in the diff. It's crucial to ensure that the function body is correctly implemented according to the specification to avoid runtime errors or incorrect behavior.

These observations are based on the provided diff and the context of the MoonBit language. It's important to review these areas to ensure the code is robust and free of potential issues.

[coveralls]

Pull Request Test Coverage Report for Build 3328

Details

• 9 of 10 (90.0%) changed or added relevant lines in 1 file are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage increased (+0.08%) to 83.283%

---

Changes Missing Coverage	Covered Lines	Changed/Added Lines	%
float/exp.mbt	9	10	90.0%

Totals
Change from base Build 3326:	0.08%
Covered Lines:	4100
Relevant Lines:	4923

---

💛 - Coveralls