Merge commit 'd2b1030060d3c91d5f9ffa3456418da16bd74f1d'

1 files changed, 6 insertions, 0 deletions

diff --git a/docs/content/en/functions/cond.md b/docs/content/en/functions/cond.md
index 16c1f105f..72a9c0a9a 100644
--- a/docs/content/en/functions/cond.md
+++ b/docs/content/en/functions/cond.md
@@ -24,3 +24,9 @@ Example:
 ```
 
 Would emit "goose" if the `$geese` array has exactly 1 item, or "geese" otherwise.
+
+{{% warning %}}
+Whenever you use a `cond` function, *both* variable expressions are *always* evaluated. This means that a usage like `cond false (div 1 0) 27` will throw an error because `div 1 0` will be evaluated *even though the condition is false*.
+
+In other words, the `cond` function does *not* provide [short-circuit evaluation](https://en.wikipedia.org/wiki/Short-circuit_evaluation) and does *not* work like a normal [ternary operator](https://en.wikipedia.org/wiki/%3F:) that will pass over the first expression if the condition returns `false`.
+{{% /warning %}}
\ No newline at end of file