Restrict actionstate computation when max-nondef-actions is not used.

Issue #52 new
geisserf created an issue

Currently, in all possible actionstates are generated (while considering possible concurrent actions) and impossible actionstates are pruned afterwards. If max-nondef-actions is not used, this generates exponential many action states, even if most of them are pruned afterwards. In the worst case this results in memory overflow and crashes the parser.

A better way would be to incorporate the action preconditions at the time when actionstates are generated.

Comments (0)

  1. Log in to comment