Anton Trunov

This is a nice suggestion! I was thinking of introducing new syntax to do that: the so-called [nullish coalescing operator](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/Nullish_coalescing) `??` (and we can support the [nullish coalescent assignment](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/Nullish_coalescing_assignment) operator...

So your example will become ```tact let a: Int?; let b: Int = 5; b += a ?? 3; ```

We should also consider updating Node.js to at least v20 and TypeScript to v5

> We should also consider updating Node.js to at least v20 and TypeScript to v5 This was done done

Let's keep this one open for now. There are ways to address this. Just not right now

What happens if we replace `external() { 42; }` with, for instance, `external() { }` (external with the empty body)?

It was not an API bug, but a parser bug and it's been apparently fixed in #341

@novusnota Yes, having a centralized data structure for all error messages is what we should go for

Closing this for now. We might return to this issue in the future

Looks like this is going to be easier when #212 is merged -- exit codes can then be easily returned from getters and checked in tests