Test language semantics

[anton-trunov]

Related docs issue: tact-lang/tact-docs#251

List of planned semantical tests

Expressions, statements

• In functions: pass by value of structs, maps, and contracts (i.e., parameters in functions are copies).
• In assignments: structs, maps and contracts are copied (i.e., assigned by value).
• In mutating functions: structs, maps and contracts are modified if they are the first parameter.
• Mutating functions chaining for structs, maps, contracts, integers.
• Nested maps
• Augment the tests in try-catch.spec.ts with structs, maps, and contracts.
• Check that && and || short-circuit.

Variable scoping

• Covered in a separate issue: Add variable scoping tests #288

Contracts

• Since contract copies can have their own state but still call contract functions, verify if this produces conflicting results with the original contract when calling library functions. This may include obtaining addresses, sending messages, etc.
• Check that it is possible to update the state of the original contract using a contract copy.
• Since messages are sent in a different phase, carry out tests that produce errors in the second phase for example.
• Check injectivity of addresses: two contracts with the same code but different initial data have different addresses, two contracts with the same initial data but different code have different addresses.
• Test sending messages with different sending modes.
• Test that receive("foo") takes precedence over receive(s: String) { if (s == "foo") { ... } }

Stdlib

• In the library documentation, many functions have notes and warnings describing some semantical behavior, test those.

Exit codes

• Covered in a separate issue: Add tests with all possible exit codes #174

[anton-trunov]

@jeshecdom Can you please write a small plan in my original post (you can edit it)? The first step 'structs' is already done and you already have planned to work with maps, so let's just document the plan here, in this issue