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
I have goals which, when executed, change the result of @reached_if directives further down in the dependency graph. But those @reached_if conditions appear to be evaluated once at execution start, so those changes aren't "picked up" until the next execution. Ideally, @reached_if would be evaluated only when execution reaches that goal.
The text was updated successfully, but these errors were encountered:
The rule of thumb should be that @reached_if can only rely on condition that is changed by the owning goal. This is what makes the tool sort of declarative. If we allow what you propose - this introduces imperative semantics into execution model (execution of a goal relies on previous execution of other goals and overall on goal execution order), which is not desirable.
I would propose to re-structure your goals logic to respect the rule of thumb above.
I can try to provide better advice if you post some sample codes that demonstrate your issue.
xonixx
changed the title
Don't evaluate @reached_if until the
Don't evaluate @reached_if until the
Feb 7, 2022
I have goals which, when executed, change the result of
@reached_if
directives further down in the dependency graph. But those@reached_if
conditions appear to be evaluated once at execution start, so those changes aren't "picked up" until the next execution. Ideally,@reached_if
would be evaluated only when execution reaches that goal.The text was updated successfully, but these errors were encountered: