about summary refs log tree commit diff
path: root/tvix/eval/docs
diff options
context:
space:
mode:
authorsterni <sternenseemann@systemli.org>2022-09-06T19·29+0200
committerclbot <clbot@tvl.fyi>2022-09-11T20·02+0000
commitcbde0292b6d029b54cf4d8ef413a6f68adbb9acf (patch)
tree0026eab3701cd120a4cc9ec839d709d9375ddf3d /tvix/eval/docs
parent6ab73c48f66a09c917ab1d3d1fb4634a224bc46f (diff)
docs(tvix/eval): mention `?` and `or` for builtins optimisation r/4820
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
Diffstat (limited to 'tvix/eval/docs')
-rw-r--r--tvix/eval/docs/known-optimisation-potential.md4
1 files changed, 3 insertions, 1 deletions
diff --git a/tvix/eval/docs/known-optimisation-potential.md b/tvix/eval/docs/known-optimisation-potential.md
index 20884519cc..fad773d7da 100644
--- a/tvix/eval/docs/known-optimisation-potential.md
+++ b/tvix/eval/docs/known-optimisation-potential.md
@@ -55,7 +55,9 @@ optimisations, but note the most important ones here.
   When accessing identifiers like `builtins.foo`, the compiler should
   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
-  `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
   definitely resolve statically.