Fix an issue with rules introducing loops #16
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I hit a bug using dagon with scalding where we have an explicit
Fork
node in the AST. This node was originally to allow the user to hint that we consumed something more than once.It turns out to be convenient to use that in planning since in an early phase I could make all forks explicit, which simplifies writing the matching rules. However, this actually causes an infinite loop.
I added some tests to expose the bug, then fixed the issue.
I want to use this in scalding so I am hoping to publish a minor fix soon.