feat: new TVM instructions in stdlib

[Gusarich]

Closes #324

• I have updated CHANGELOG.md
• 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 did not do unrelated and/or undiscussed refactorings

[Gusarich]

Seems like https://github.com/tact-lang/tact-emulator doesn't support new opcodes yet: I'm getting Invalid opcode error in tests.

[anton-trunov]

Seems like https://github.com/tact-lang/tact-emulator doesn't support new opcodes yet: I'm getting Invalid opcode error in tests.

Looks like you are getting @tact-lang/emulator@4.2.3 instead of 4.3.0 in CI

warning " > @tact-lang/emulator@4.2.3" has unmet peer dependency "ton-abi@^0.0.1".

You might need to update the yarn.lock file (and package.json too, although it uses ^ for the emulator package)

[Gusarich]

Depends on tact-lang/tact-emulator#13

[Gusarich]

I guess since we won't use tact emulator anymore after the merge of #651, we can ignore that issue and finish this stdlib update.

[anton-trunov]

That would be awesome!

[anton-trunov]

Some old comments of mine + a new one

[anton-trunov]

Looks like you also need to commit the changes to the generated stdlib.ts

[anton-trunov]

@Gusarich Looks like after #768 this can be implemented directly in Tact

[anton-trunov]

@Gusarich Any progress on this?

[Gusarich]

@Gusarich Looks like after #768 this can be implemented directly in Tact

yes, but I think we can keep this PR as it's now and do that for future stdlib updates

[anton-trunov]

I think we can keep this PR as it's now and do that for future stdlib updates

Let's do a bit of doogfooding here: the more we use our own language features for the stdlib the less bugs those are going to have. And this is important because we are going to do a new release pretty soon

[Gusarich]

I think we can keep this PR as it's now and do that for future stdlib updates

Let's do a bit of doogfooding here: the more we use our own language features for the stdlib the less bugs those are going to have. And this is important because we are going to do a new release pretty soon

then what about all other functions from stdlib? Many of them are used in writeStdlib.ts so we can't just rewrite them natively in Tact.

[anton-trunov]

then what about all other functions from stdlib? Many of them are used in writeStdlib.ts so we can't just rewrite them natively in Tact.

It's fine. If it cannot be done easily (at least now), let's not do it. When I ported some stdlib functions to use asm-blocks instead of a FunC binding, I wasn't trying to go overboard with that.

[Gusarich]

@anton-trunov so should I move the new functions from stdlib.fc to Tact stdlib for this PR?

[anton-trunov]

@anton-trunov so should I move the new functions from stdlib.fc to Tact stdlib for this PR?

Yes, let's go for it

[anton-trunov]

LGTM. Just the specllchecker complaints. Btw, we do have Knip now with pre-push lints running automatically and those include spellchecking

[Gusarich]

LGTM. Just the specllchecker complaints. Btw, we do have Knip now with pre-push lints running automatically and those include spellchecking

fixed