-
-
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 quickly deploy the updated tact-docs and not se…
-
### Observed behaviour
Upon compilation error, user sees a cryptic "Error while building" message in the log output. And that's it, no details.
### Expected behavior or possible solutions
Tac…
-
This is a very incomplete draft proposal for the next major version of Tact. Comments are most welcome.
## Grammar
- ignore `...` (or something else) -- useful for parsing incomplete examples in…
-
If I uncomment the commented out line in `receive(_: Foo)`, the tests work as expected and the child contract gets deployed. Otherwise, the tests fail with exit code 135: `Code of a contract was not f…
-
Tact should add support for `Either` TL-B type.
I propose we use the `?` operator: TL-B `Either X Y` -> Tact `X ? Y`. If it's too confusing we could also use a more explicit syntax `Either`.
0kenx updated
2 weeks ago
-
For that, use `:error` attribute in tests, see: https://tree-sitter.github.io/tree-sitter/creating-parsers
Alternatively (or additionally?), a simple check can be added to CI, which would take the …
-
When specifying a non-existent FunC identifier (neither in stdlib.fc nor in imported FunC code), Tact doesn't catch that and the error leaks to FunC, where compilation errors with a misleading message…
-
For instance, add the following command line options:
- [x] `--version` / `-v`: output Tact's version (done in #137)
- [ ] https://github.com/tact-lang/tact/issues/504
- [x] `--help` / `-h`: output…
-
There are a few possible ways to improve the Tact frontend API that would be helpful for tooling:
* [ ] Improve workflow with `{Node,Virtual}FileSystem` API. These functions should have improved do…