Skip to content

A bunch of stuff#295

Draft
rayman2000 wants to merge 20 commits into
masterfrom
nklose/qol-and-errors
Draft

A bunch of stuff#295
rayman2000 wants to merge 20 commits into
masterfrom
nklose/qol-and-errors

Conversation

@rayman2000

@rayman2000 rayman2000 commented Mar 26, 2026

Copy link
Copy Markdown
Collaborator
  • Improved the error message for unsupported features
  • Fixed a bug in list_mul: the values in the result were being calculated incorrectly
  • Added support for list.insert: the insert index is complicated, if it is greater than the length, then we append at the end. If it is negative, we go backwards from the end of the list, if negative and greater than the length, we prepend.

This change is Reviewable

@rayman2000

Copy link
Copy Markdown
Collaborator Author
  • Changed the encoding of contains for lists and PSeqs. They now state that an element exists in the collection that object-equals the input.

@rayman2000

Copy link
Copy Markdown
Collaborator Author
  • Added --strict-int mode, which replaces many instances of isinstance(x, int) with type(x) == int in the Viper encoding.

@rayman2000

Copy link
Copy Markdown
Collaborator Author
  • Added support for (some) CLI arguments in server client mode

@rayman2000

Copy link
Copy Markdown
Collaborator Author
  • Added handling for Silicon Timeout Exceptions

rayman2000 and others added 11 commits April 15, 2026 16:06
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
# Conflicts:
#	src/nagini_translation/client.py
#	src/nagini_translation/main.py
#	src/nagini_translation/resources/builtins.json
#	tests/functional/verification/test_lists.py
Threads strict_int through both service translate call sites, the
configure tool (strictInt), and the shared service CLI arguments so
nagini_mcp/nagini_lsp can run in strict-int mode. force_obligations
pins the obligation encoding via the existing snapshot mechanism.
Also threads strict_int through the CLI benchmark path.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
The implicit 'return type is correct' postcondition error is now
reported on the function definition rather than the return statement.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@rayman2000 rayman2000 changed the title Smaller fixes A bunch of stuff Jul 8, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant