ton/tolk-tester/tests/invalid-mutate-5.tolk

fun cantCallMutatingMethod(c: cell) {
    val s: slice = c.beginParse();
    if (1) {
        var s: slice = c.beginParse();
        s.loadRef();       // this is ok, 's' is another variable
    }
    val i = s.loadUint(32);
}

/**
@compilation_should_fail
@stderr modifying immutable variable `s`
@stderr s.loadUint
 */
[Tolk] Get rid of ~tilda with `mutate` and `self` methods This is a very big change. If FunC has `.methods()` and `~methods()`, Tolk has only dot, one and only way to call a `.method()`. A method may mutate an object, or may not. It's a behavioral and semantic difference from FunC. - `cs.loadInt(32)` modifies a slice and returns an integer - `b.storeInt(x, 32)` modifies a builder - `b = b.storeInt()` also works, since it not only modifies, but returns - chained methods also work, they return `self` - everything works exactly as expected, similar to JS - no runtime overhead, exactly same Fift instructions - custom methods are created with ease - tilda `~` does not exist in Tolk at all 2024-10-31 07:18:54 +00:00			`fun cantCallMutatingMethod(c: cell) {`
			`val s: slice = c.beginParse();`
			`if (1) {`
			`var s: slice = c.beginParse();`
			`s.loadRef(); // this is ok, 's' is another variable`
			`}`
			`val i = s.loadUint(32);`
			`}`

			`/**`
			`@compilation_should_fail`
[Tolk] AST-based semantic analysis, get rid of Expr This is a huge refactoring focusing on untangling compiler internals (previously forked from FunC). The goal is to convert AST directly to Op (a kind of IR representation), doing all code analysis at AST level. Noteable changes: - AST-based semantic kernel includes: registering global symbols, scope handling and resolving local/global identifiers, lvalue/rvalue calc and check, implicit return detection, mutability analysis, pure/impure validity checks, simple constant folding - values of `const` variables are calculated NOT based on CodeBlob, but via a newly-introduced AST-based constant evaluator - AST vertices are now inherited from expression/statement/other; expression vertices have common properties (TypeExpr, lvalue/rvalue) - symbol table is rewritten completely, SymDef/SymVal no longer exist, lexer now doesn't need to register identifiers - AST vertices have references to symbols, filled at different stages of pipeline - the remaining "FunC legacy part" is almost unchanged besides Expr which was fully dropped; AST is converted to Ops (IR) directly 2024-12-16 18:19:45 +00:00			@stderr modifying immutable variable `s`
[Tolk] Get rid of ~tilda with `mutate` and `self` methods This is a very big change. If FunC has `.methods()` and `~methods()`, Tolk has only dot, one and only way to call a `.method()`. A method may mutate an object, or may not. It's a behavioral and semantic difference from FunC. - `cs.loadInt(32)` modifies a slice and returns an integer - `b.storeInt(x, 32)` modifies a builder - `b = b.storeInt()` also works, since it not only modifies, but returns - chained methods also work, they return `self` - everything works exactly as expected, similar to JS - no runtime overhead, exactly same Fift instructions - custom methods are created with ease - tilda `~` does not exist in Tolk at all 2024-10-31 07:18:54 +00:00			`@stderr s.loadUint`
			`*/`