tact-docs
tact-docs copied to clipboard
Tact main documentation
Like #115, but for Traits. * Differences with contracts: * no `init()`, that's only for contracts * keywords: `virtual` and `abstract` (in trait) and `override` (in contract) * `@interface` —...
It needs: * Better formatting * More throrough description of attributes (`extends`, `mutates`, etc.) * Mention of `receive()`, `external()`, `bounced()` with links to relevant pages Will resolve #129.
* Middleware and routing should enable language switching (`next.config.js` + new `middleware.js` in the root) * All the pages should get their empty Chinese counterparts, so that Chinese translators may...
Add one section about debugging contracts in general Add the `dump` function to the reference of static available functions
Anti-patterns: - [ ] on-chain string parsing from a human-friendly format into a machine-readable binary structure -- a dapp frontend should do that and only communicate with its smart contracts...
Related issue: #146 Also, it would be nice to have an example of adding liquidity (as suggested by @Gusarich)
Related issue: #149 Also, it would be nice to have an example of adding liquidity (as suggested by @Gusarich)
What if the incoming funds are excessive and we want to refund the excess back? (The docs never mention the word "refund")
What happens if I try to use recursion in contract methods, standalone functions or getters? The answer should include mutual recursion too.
For instance, if I have something like this: ```tact fun foo() { ... } fun bar() { ... } ``` `bar` should be able to refer to `foo`, but can...