mirror of
https://github.com/ton-blockchain/ton
synced 2025-03-09 15:40:10 +00:00
1389ff6789
In FunC (and in Tolk before), the assignment > lhs = rhs evaluation order (at IR level) was "rhs first, lhs second". In practice, this did not matter, because lhs could only be a primitive: > (v1, v2) = getValue() Left side of assignment actually has no "evaluation". Since Tolk implemented indexed access, there could be > getTensor().0 = getValue() or (in the future) > getObject().field = getValue() where evaluation order becomes significant. Now evaluation order will be to "lhs first, rhs second" (more expected from user's point of view), which will become significant when building control flow graph.
8 lines
153 B
Text
8 lines
153 B
Text
fun main(cs: slice) {
|
|
var cb = cs.tupleSize;
|
|
}
|
|
|
|
/**
|
|
@compilation_should_fail
|
|
@stderr referencing a method for `tuple` with object of type `slice`
|
|
*/
|