-
For instance, https://github.com/Wilfred/difftastic -- Difftastic is a structural diff tool that compares files based on their syntax. It should not be hard to add Tact support to Difftastic since it …
-
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 …
-
Currently, [tact-vscode](https://github.com/tact-lang/tact-vscode) does source code formatting using a plugin for [Prettier](https://prettier.io).
I believe a formatter should be a part of the langua…
-
Additionally, Go bindings (and, maybe, some others) may require some updates — for that, tree-sitter-tact may have to get submitted in the community bindings repositories, like [smacker/go-tree-sitter…
-
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 …
-
This can be done using `tree-sitter-cli` itself:
```shell
tree-sitter build --wasm
```
Examples in the docs: https://tree-sitter.github.io/tree-sitter/creating-parsers#command-build
-
It should be in principle possible, since GitHub uses it in Linguist.
No more regex-based highlighting! :)
This would make things like #183 much easier
-
## Context
It's often nice to quickly check the outputs, possible errors, boundaries or gas usage of Tact code without writing lots of Jest tests, which slow down the speed of such exploration (IMO…
-
This should include VS Code plugins for Tact, FunC & installed dependencies for contributing to docs.
More on Codespaces: https://github.com/features/codespaces.
Depends on #89 and #88.
-
I have something like this in my config:
```lua
vim.api.nvim_create_autocmd({ "BufRead", "BufNewFile" }, {
pattern = "*.org",
callback = function()
require("otter").activate()
end,
})…