feat(frontend): Acosd function

[CAJan93]

I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.

What's changed and what's your intention?

Implement the Acosd function. This implementation is slightly different from the PSQL implementation. I do not return an error on acosd(Inf), but instead return NaN. Also returns NaN when inout is out of range.

• Tracking Issue
• PSQL implementation

Checklist For Contributors

• I have written necessary rustdoc comments
• I have added necessary unit tests and integration tests
• I have added fuzzing tests or opened an issue to track them. (Optional, recommended for new SQL features Sqlsmith: Sql feature generation #7934).
• I have demonstrated that backward compatibility is not broken by breaking changes and created issues to track deprecated features to be removed in the future. (Please refer to the issue)
• All checks passed in ./risedev check (or alias, ./risedev c)

Checklist For Reviewers

• I have requested macro/micro-benchmarks as this PR can affect performance substantially, and the results are shown.

Documentation

• My PR DOES NOT contain user-facing changes.

Click here for Documentation

Types of user-facing changes

acosd trigonometric function implementation.

Release note

Add acosd function, which calculates the inverse acos in degrees.

[github-actions]

This PR has been open for 60 days with no activity. Could you please update the status? Feel free to ping a reviewer if you are waiting for review.

[gitguardian]

⚠️ GitGuardian has uncovered 4 secrets following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secrets in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
9425213	Triggered	Generic Password	a271c3c	ci/scripts/e2e-source-test.sh	View secret
9425213	Triggered	Generic Password	a271c3c	ci/scripts/e2e-sink-test.sh	View secret
9425213	Triggered	Generic Password	a271c3c	ci/scripts/e2e-source-test.sh	View secret
9425213	Triggered	Generic Password	a271c3c	ci/docker-compose.yml	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secrets safely. Learn here the best practices.
3. Revoke and rotate these secrets.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}

[CAJan93]

@xiangjinwu Sorry, I completely forgot about this one. Does this LGTY?

[xiangjinwu]

@xiangjinwu Sorry, I completely forgot about this one. Does this LGTY?

No worries. We received no requests from customers needing trigonometric functions 😂

[CAJan93]

No worries. We received no requests from customers needing trigonometric functions 😂

Guess so 😂 Was still nice to work on the kernel side for a while.

[CAJan93]

No idea why we get these imprecisions. Doing everything just like the PG implementation. Maybe it is a difference between Rust and C?

For now I will hardcode these cases. I feel like it is not wort putting more energy into this.

SELECT x,
       tand(x),
       tand(x) IN ('-Infinity'::float8,-1,0,
                   1,'Infinity'::float8) AS tand_exact,
       cotd(x),
       cotd(x) IN ('-Infinity'::float8,-1,0,
                   1,'Infinity'::float8) AS cotd_exact
FROM (VALUES (0), (45), (90), (135), (180),
      (225), (270), (315), (360)) AS t(x);
2024-06-27T17:28:44.720818Z ERROR risingwave_regress_test::schedule: Diff:
-  x  |   tand    | tand_exact |   cotd    | cotd_exact
------+-----------+------------+-----------+------------
-   0 |         0 | t          |  Infinity | t
-  45 |         1 | t          |         1 | t
-  90 |  Infinity | t          |         0 | t
- 135 |        -1 | t          |        -1 | t
- 180 |         0 | t          | -Infinity | t
- 225 |         1 | t          |         1 | t
- 270 | -Infinity | t          |         0 | t
- 315 |        -1 | t          |        -1 | t
- 360 |         0 | t          |  Infinity | t
+  x  |        tand         | tand_exact |        cotd         | cotd_exact
+-----+---------------------+------------+---------------------+------------
+   0 |                   0 | t          |            Infinity | t
+  45 |  1.0000000000000002 | f          |  0.9999999999999998 | f
+  90 |            Infinity | t          |                   0 | t
+ 135 | -1.0000000000000002 | f          | -0.9999999999999998 | f
+ 180 |                   0 | t          |           -Infinity | t
+ 225 |  1.0000000000000002 | f          |  0.9999999999999998 | f
+ 270 |           -Infinity | t          |                   0 | t
+ 315 | -1.0000000000000002 | f          | -0.9999999999999998 | f
+ 360 |                   0 | t          |            Infinity | t

[CAJan93]

Shall we merge it @xiangjinwu ? 😁 If we really don't need the function at the moment I'd suggest to close the PR.

[xiangjinwu]

Shall we merge it @xiangjinwu ? 😁 If we really don't need the function at the moment I'd suggest to close the PR.

I am looking at several avro issues recently 🥵

[CAJan93]

I am looking at several avro issues recently 🥵

No worries. I think this is low priority 😁