You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When there is a conditional template and the expression evaluates to false, the renderer jumps over the end template, resulting in the conditional stack not popping. This leads to very rare unexpected behavior that is very hard to predict. For example, in some cases, the renderer enters an else conditional template even if the previous conditional is true. This happens because the renderer retrieves information from another conditional template info structure, which was not popped and reports that the last conditional was false (thus resulting in the else conditional being rendered).
The problem is that the compiler emits the jump index after the end template, when it should emit it right before (such that the pop operation occurs).
The text was updated successfully, but these errors were encountered:
When there is a conditional template and the expression evaluates to false, the renderer jumps over the end template, resulting in the conditional stack not popping. This leads to very rare unexpected behavior that is very hard to predict. For example, in some cases, the renderer enters an else conditional template even if the previous conditional is true. This happens because the renderer retrieves information from another conditional template info structure, which was not popped and reports that the last conditional was false (thus resulting in the else conditional being rendered).
The problem is that the compiler emits the jump index after the end template, when it should emit it right before (such that the pop operation occurs).
The text was updated successfully, but these errors were encountered: