feat: new functions in stdlib from stdlib.fc and math.fc

[Gusarich]

Issue

Closes #770
Towards #1029 (only myCode())

Checklist

• I have updated CHANGELOG.md
• I have documented my contribution in docs/ and made the build locally
• I have added tests to demonstrate the contribution is correctly implemented: this usually includes both positive and negative tests, showing the happy path(s) and featuring intentionally broken cases
• I have run all the tests locally and no test failure was reported
• I have run the linter, formatter and spellchecker
• I did not do unrelated and/or undiscussed refactorings

Current State

• All stdlib.fc functions are present in Tact stdlib in some form, with some exceptions:
  • no tuple manipulation functions, because there is no tuple support in Tact. Do we really need them? @anton-trunov
  • no minmax and no slice_bits_refs because we don't have tensor types in Tact and it would be useless: Tensor types #1116
  • no set_data and get_data because Tact manages persistent storage by itself
  • no bless and other continuation functions because Tact manages control flow itself and for running some arbitrary code it's better to use RUNVM which doesn't require continuations parameters
  • no raw_reserve_extra because it requires an uint32 -> varuint32 dictionary and we only support varuint16 for values currently: VarUInt32, VarInt16, VarInt32 serialization types #1117
• All mathlib.fc functions are present in Tact stdlib in some form, with some exceptions:
  • no fixed-point arithmetic related functions: Fixed-point arithmetics library #1118
  • no nan and is_nan because we don't support NaN in Tact. Do we really need them? @anton-trunov
  • no sub_rev because it is useless in our case
  • no ...MOD instructions because they return two values as a tensor and it won't be very developer-friendly in Tact to make them return tuples in my opinion: Tensor types #1116
• All new functions are covered with tests

[novusnota]

Sorry for reviewing the draft, I just wanted to keep those notes around :)

[Gusarich]

@novusnota @anton-trunov Implemented all functions. I'd like to hear some intermediate feedback on them before I proceed with writing tests.

I made sure to include all missing functions from both stdlib.fc and mathlib.fc with some exceptions (see PR description).

[anton-trunov]

afair, mathlib.fc has lots of functions for fixed-arithmetic as well, I think we should add those too (perhaps as a separate library, like fixed_point_math.tact).

Also, I left a couple comments in the source code

[Gusarich]

@anton-trunov @novusnota covered all new functions with tests!

Found and fixed a few little mistakes in types (for addressNone and computeDataSize functions). Also added comments with formulas for new math functions

[anton-trunov]

@Gusarich Let's

• resolve the merge conflicts
• move the notes from "current state" to their own separate issues

[anton-trunov]

We should document the new functions in https://docs.tact-lang.org/ref/core-math and other relevant doc pages

[novusnota]

We should document the new functions in https://docs.tact-lang.org/ref/core-math and other relevant doc pages

Will do

[novusnota]

macOS CIs exceed some time limits even after restarting those in isolation. Other than that, this PR seems to be done, I've even added the couple of "gas-expensive" badges :)

We should document the new functions in https://docs.tact-lang.org/ref/core-math and other relevant doc pages

✔️

[anton-trunov]

Almost done, just one final push

[novusnota]

Let's finally merge this :)

[novusnota]

Uno momento

[novusnota]

@i582 Resolved your suggestions (hopefully), please take a look

[i582]

LGTM

[novusnota]

Hooray 🎉