Anton Trunov

Perhaps we could also test auto-completion, so that issues like #18 once resolved never appear again

> enable Actions tab in the settings of this repo done

> and then grepping the logs for errors & such Does Vim have some sort of (stable) API that we can use for this task? Grepping makes it brittle

@tolk-vm This issue still persists for FunC 0.4.6: ```shell ❯ npx func-js --fift wasm_test.fif wasm_test.fc Compiling using func v0.4.6 wasm://wasm/0150db3e:1 RuntimeError: table index is out of bounds at wasm://wasm/0150db3e:wasm-function[4278]:0x190c4c at...

@skulidropek btw, not sure if this helps, maybe you can tell: we have some recommendations on gas optimizations for Tact contracts, is it possible to somehow incorporate these: https://github.com/tact-lang/tact/issues/1868?

[Exploratory programming](https://en.wikipedia.org/wiki/Exploratory_programming) is indeed a really nice technique! I love it myself, e.g. all kinds of [REPLs](https://en.wikipedia.org/wiki/Read–eval–print_loop) and tools like that and would very much like it to be integrated...

This is a very useful project and it's already being implemented: https://github.com/tact-lang/tact/pull/335.

@delovoyhomie We just merged the formatter prototype into the Tact codebase.

I like the idea of adding this kind of stuff to the docs! There is a related issue already: https://github.com/tact-lang/tact/issues/1168

> or consider another small CLI tool to bin/ just like you recently did with unboc. yep, this is exactly what's going on here :)