r0ller/alice

semantic rule substeps need to be ordered according their length of dependencies

r0ller opened this issue · 1 comments

Currently, in each step, one substep is expected to get executed in case the step itself not being optional. If there are e.g. two substeps where the first one has less dependencies than the other, that can be validated in the current interpretation, then the interpretation stops checking further in is_valid_combination() after the successful validation of the first one. The workaround is to enter the substeps in a way that the substep with the longest number of dependencies comes first and then the rest in descending order.

Not relevant, as stepping in rule_to_rule_map got redesigned to allow both positive and negative branching while substeps aren't used any more.