mdebray/tvl-depot
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

docs(tvix/eval): mention ? and or for builtins optimisation

Browse source 
Change-Id: Ifaa6da345d408a69ce46d6a0e7483352715c75bd
Reviewed-on: https://cl.tvl.fyi/c/depot/+/6525
Autosubmit: sterni <sternenseemann@systemli.org>
Reviewed-by: tazjin <tazjin@tvl.su>
Tested-by: BuildkiteCI
This commit is contained in:
sterni 2022-09-06 21:29:58 +02:00 committed by clbot
parent 6ab73c48f6
commit cbde0292b6
1 changed files with 3 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
tvix/eval/docs/known-optimisation-potential.md
View file

@ -55,7 +55,9 @@ optimisations, but note the most important ones here.
When accessing identifiers like `builtins.foo`, the compiler should When accessing identifiers like `builtins.foo`, the compiler should
not go through the trouble of setting up the attribute set on the not go through the trouble of setting up the attribute set on the
stack and accessing `foo` from it if it knows that the scope for stack and accessing `foo` from it if it knows that the scope for
`builtins` is unpoisoned. `builtins` is unpoisoned. The same optimisation can also be done
for the other set operations like `builtins ? foo` and
`builtins.foo or alternative-implementation`.
The same thing goes for resolving `with builtins;`, which should The same thing goes for resolving `with builtins;`, which should
definitely resolve statically. definitely resolve statically.