Repository navigation
Rename the UNPROVABLE error category to UNKNOWN - #431
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
[Codex review] The internal rename is consistent: the category ID stays C4.2, the diagnostic and hint branches use |
|
[Claude] Good point. The PR description now documents this as an API break: |
Renames the C4.2 error category from
UNPROVABLEtoUNKNOWN. Every refinement error means the verifier could not prove something, so "unprovable" does not set this case apart. What does is that nothing is known about the value or state.ErrorCategory:UNPROVABLE→UNKNOWN, title now starts with "Unknown:"RefinementError,StateErrorCategoriesandStateHintsuse the new nameErrorUnprovableArgument.java→ErrorUnknownArgument.java, test methods inTestErrorCategoriesrenamedNo behaviour change in verification. The codebook ID (C4.2) is unchanged.
API break:
ErrorCategoryis public and returned byLJDiagnostic.getCategory(), so clients that referenceErrorCategory.UNPROVABLEno longer compile, and serialized enum names change fromUNPROVABLEtoUNKNOWN. No client in the organisation (vscode-liquidjava, liquidjava-mcp) uses the old name. Releases after 0.0.36 carry this change.Tests:
mvn -pl liquidjava-verifier -am testpasses (496 tests, 0 failures).🤖 Generated with Claude Code