tact-docs

tact-docs copied to clipboard

Closes #231 Alternatively, we may just send `null` in `self.notify()`, but that would be less descriptive, so I went with the same approach used in `@stdlib/deploy`.

novusnota

Fix counter example on landing page to return excess TONs to contract deployer

2

Let's say the deployer sends 0.05 TONs during contract deployment. They should get the excess back

anton-trunov

Check if there are more undocumented builtin functions

5

see for example #162

anton-trunov

Complete annotated grammar reference/spec from `grammar.ohm`

1

Current [grammar page](https://docs.tact-lang.org/language/guides/grammar) doesn't bring much value, especially for those willing to work on Tact compiler development or related tooling. The page should be moved to the Language → Reference...

novusnota

Related to #127. Asked by @reveloper

anton-trunov

Variable scoping is not documented

4

For instance, is variable shadowing allowed?

anton-trunov

book/import#import-func-code lacks examples of importing FunC functions returning tuples

2

As Tact does not have tuple types (at least yet), like FunC does, importing such functions is challenging for users: For instance, how does one import a function like the...

anton-trunov

And more info about contract interaction in general. Additionally, add relevant examples to the Cookbook. This may get split into separate issues. See: * https://tact-by-example.org/06-multiple-contract-instances * https://tact-by-example.org/06-contract-deploy-another * https://tact-by-example.org/06-communicating-subcontract *...

novusnota

We actually evaluate constant expressions at compile-time and need to document constraints like, for instance, Rust does: https://doc.rust-lang.org/reference/const_eval.html

anton-trunov

Goes beyond the Tact 1.3.0 and covers previous versions as well. In progress, alongside the new Sublime Text package.

novusnota