Branch stack effects

Factor handbook » The language » Stack effect checking

Factor handbook » The language » Stack effect checking

Prev: | Recursive combinator stack effects |

Next: | Stack checker errors |

Conditionals such as if and combinators built on top have the same restrictions as inline combinators (see Combinator stack effects) with the additional requirement that all branches leave the stack at the same height. If this is not the case, the stack checker throws an unbalanced-branches-error.

If all branches leave the stack at the same height, then the stack effect of the conditional is just the maximum of the stack effect of each branch. For example,

The call to if takes one value from the stack, a generalized boolean. The first branch [ + ] has stack effect ( x x -- x ) and the second has stack effect ( x -- ). Since both branches decrease the height of the stack by one, we say that the stack effect of the two branches is ( x x -- x ), and together with the boolean popped off the stack by if, this gives a total stack effect of ( x x x -- x ).

If all branches leave the stack at the same height, then the stack effect of the conditional is just the maximum of the stack effect of each branch. For example,

[ [ + ] [ drop ] if ] infer.

( x x x -- x )

( x x x -- x )

The call to if takes one value from the stack, a generalized boolean. The first branch [ + ] has stack effect ( x x -- x ) and the second has stack effect ( x -- ). Since both branches decrease the height of the stack by one, we say that the stack effect of the two branches is ( x x -- x ), and together with the boolean popped off the stack by if, this gives a total stack effect of ( x x x -- x ).

This documentation was generated offline from a
`load-all`

image. If you want, you can also
browse the documentation from within the UI developer tools. See
the Factor website
for more information.

Factor 0.101 x86.64 (2282, heads/master-74be1555ff, Sep 25 2024 19:43:38)