Check for unknown labels in usage commands #177
Merged
Conversation
This file contains 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.
Because the
usagecommand was checking the database in a single pass, it did not know about axioms after the current cursor, and was assuming that these axioms existed and were not used.However, this has the side effect of not being able to report unknown labels in usage commands.
This PR fixes this, and reports unknown labels in usage commands.
One test added.
This is a follow-up of #175: Following that PR, a missing space between two
usagelabels like in$j 'exel' avoids 'ax-10''ax-13';will now be parsed as refering toax-10'ax-13(doubled quote as escape). To be complete, the tool now needs to report this unknown label.