tact-docs
tact-docs copied to clipboard
tact-lang
Tact main documentation
Contracts, traits, native functions, function parameters, let-variables, foreach binders, declared primitive types, structures and messages cannot be named with identifiers that start with `__gen` or `__tact`
Ecosystem→Tools: * [Nujan Web-based IDE](https://ide.nujan.io/) — at least a reference to it would be nice * [Blueprint](https://github.com/ton-community/blueprint) — common development environment for TON Blockchain to write, test, and deploy smart...
It would be nice to include problems as well as solutions given by the contest makers. Plus, links to solutions of the winners either directly to GitHub or via Web...
It would be nice to have simple but full config files for Neovim and Helix, so that beginners could simply download those and start immediately hack on their Tact projects....
Basically, I'd like to have a new Tact feature to be documented right after the PR that introduces it is merged, so that after a new Tact release we can...
In particular: 1. Poor formatting 2. Incomplete examples 3. Exit codes (explain the concept to later be defined by tact-lang/tact#887) 4. Lack of serialization options and details, see tact-lang/tact-docs#94 and...
Great [tact-fireworks](https://github.com/ton-community/tact-fireworks) may suit as a starting point. Furthermore, the [Fireworks contract](https://github.com/ton-community/tact-fireworks/blob/3e7c4ec23d6d663a2f8a73d1d12eef9fe0780580/contracts/fireworks.tact#L38) should be split into many smaller contracts (or `receive()` functions) to showcase one error and exit code per...
Example usage: https://github.com/tact-lang/tact/blob/6da6d5bcb87a2535466454396b6ba03abfebfdb3/examples/wallet-opt.tact#L2. See [tact/src/types/resolveABITypeRef.ts#L44](https://github.com/tact-lang/tact/blob/7ed5e05dc0fcbc880f76fe326ea03aae69a3d966/src/types/resolveABITypeRef.ts#L44)
Those tools seem to be widely used in the community and we should switch to use those consistently everywhere in the Tact docs