Checks for multiple init and next blocks and throws a parser error if encountered#262
Merged
Conversation
Contributor
Author
|
@kkmc I've disabled the code that combines init blocks in this PR, because the order they were combined in if there were two blocks written in the same module in the input file seemed to be nondeterministic e.g., this passes: and this passes: But this does not: Do you need this code for the TAP proofs? If so, we need to figure out how to combine the init blocks in the order they are parsed in |
Remove code that picks only one init block when combining modules this was previously misleading because the order the init block statements were combined in isn't obvious to the user.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
No description provided.