diff options
author | Vincent Ambo <mail@tazj.in> | 2022-08-28T03·07+0300 |
---|---|---|
committer | tazjin <tazjin@tvl.su> | 2022-09-06T07·45+0000 |
commit | 776120de05fc9f26d1af5da92d8b25ec26648365 (patch) | |
tree | 21e04f3aa6575e54d0cf4dd074a9536326502cf6 /tvix/eval/src/tests/tvix_tests/eval-okay-or-operator.nix | |
parent | ccfb971dc54cb77522d70f1ecbf1e9080e7ba0ca (diff) |
fix(tvix/eval): instantiate *new* closures from blueprints each time r/4659
The previous closure refactoring introduced a bug in which the same closure object would get mutated constantly for each instance of a closure, which is incorrect behaviour. This commit instead introduces an explicit new Value variant for the internal "blueprint" that the compiler generates (essentially just the lambda) and uses this variant to construct the closure at runtime. If the blueprint ever leaks out to a user somehow that is a critical bug and tvix-eval will panic. As a ~treat~ test for this, the fibonacci function is being used as it is a self-recursive closure (i.e. different instantiations of the same "blueprint") getting called with different values and it's good to have it around. Change-Id: I485de675e9bb0c599ed7d5dc0f001eb34ab4c15f Reviewed-on: https://cl.tvl.fyi/c/depot/+/6323 Tested-by: BuildkiteCI Reviewed-by: sterni <sternenseemann@systemli.org>
Diffstat (limited to 'tvix/eval/src/tests/tvix_tests/eval-okay-or-operator.nix')
0 files changed, 0 insertions, 0 deletions