tolk-vm 1389ff6789 [Tolk] Change order of assignment evaluation, lhs first ... 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.		2025-02-24 20:11:13 +03:00
..
tests	[Tolk] Change order of assignment evaluation, lhs first	2025-02-24 20:11:13 +03:00
tolk-tester.js	[Tolk] AST-based semantic analysis, get rid of Expr	2025-01-13 20:28:44 +07:00
tolk-tester.py	[Tolk] AST-based semantic analysis, get rid of Expr	2025-01-13 20:28:44 +07:00