Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improving error messages #182

Open
ZachJHansen opened this issue Jan 22, 2025 · 0 comments
Open

Improving error messages #182

ZachJHansen opened this issue Jan 22, 2025 · 0 comments
Labels
A-verifying Area: Verifying C-enhancement Category: Enhancement E-medium Experience: Medium L-fol Language: First-order logic P-low Priority: Low

Comments

@ZachJHansen
Copy link
Collaborator

It would be nice to catch bad user input that will produce invalid TPTP files before piping that output to Vampire. The Vampire error messages can be too cryptic. A common issue is that a misnamed or missing variable in a quantification can produce a syntactically valid formula, but when passed to Vampire the variable is treated as type "$i" (Vampire's generic) rather than Anthem's $g, producing a semantic error. For example,

assumption: forall V X p(X, Y).

contains a typo (V should be called Y, or vice versa) but the bug doesn't get caught until Vampire produces the message

% Exception at proof search level
Parsing Error on line 35
Argument 2 of predicate p expected something of sort general but got something of sort $i

@ZachJHansen ZachJHansen added A-verifying Area: Verifying C-enhancement Category: Enhancement E-medium Experience: Medium L-fol Language: First-order logic P-low Priority: Low labels Jan 22, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-verifying Area: Verifying C-enhancement Category: Enhancement E-medium Experience: Medium L-fol Language: First-order logic P-low Priority: Low
Projects
None yet
Development

No branches or pull requests

1 participant