Anton Trunov

You are totally right, well-typed Tact code should not provoke any FunC typechecking errors. Will fix the concrete [example](https://github.com/tact-lang/tact/issues/118#issuecomment-1879258362) you provided in Tact v1.3.0 release most likely. Although it's hard...

@Gusarich I'm wondering if this can be replicated with `@ton-community/func-js` since we basically re-use a wasm build of FunC. We could create an issue there and see if someone resolves...

@xfhxfh2021 Thanks for your report. Could you please provide an [MRE](https://en.wikipedia.org/wiki/Minimal_reproducible_example)? That would help us immensely.

This is expected behavior: please read this explanation https://docs.tact-lang.org/book/send#outbound-message-processing

It's probably worth adding that `emit` essentially sends a message, so the explanation above applies to this case too

@novusnota I like your suggestion better

The issue here is that constant evaluation is performed on a non-typechecked AST. So when you call `getExpType` to dispatch on the type of `==` / `!=` operators, there is...

Looks like this PR should be closed now? Because the architecture of the constant evaluator has changed a lot in #432. Of course, we can still improve a lot of...

@vitorpy Sure! Feel free to give it a try. I should probably tell you that implementing string interpolation is usually far from trivial. This is why I didn't assign a...

What is the difference between this issue and #77?