Update Charon submodule to v0.1.69#4660
Open
tautschnig wants to merge 1 commit into
Open
Conversation
Advance the Charon pin from v0.1.68 (63f7749d) to v0.1.69 (485bd36e), the next step of the incremental effort to catch the pinned Charon up with upstream (the endgame is dropping scripts/charon-patch.diff entirely). Charon v0.1.69 makes `Vector::elem_count` the way to obtain the number of non-empty slots (`len` is removed); adapt the tuple-field-projection translation in the LLBC backend accordingly. Refresh scripts/charon-patch.diff so its hunks apply against the v0.1.69 sources (context-line drift only; the patch content is unchanged). Co-authored-by: Kiro <kiro-agent@users.noreply.github.com>
github-actions
Bot
added
Z-EndToEndBenchCI
Contributor
There was a problem hiding this comment.
Pull request overview
This PR advances the pinned Charon version to v0.1.69 and updates Kani’s LLBC backend to match the upstream API change where Vector::len is removed in favor of Vector::elem_count, ensuring tuple-field-projection translation continues to compute tuple arity correctly.
Changes:
- Update the Charon dependency pin to v0.1.69 (including
Cargo.lock). - Adapt LLBC tuple projection translation to use
genargs.types.elem_count()instead oflen(). - Refresh
scripts/charon-patch.diffso it applies cleanly against the v0.1.69 sources (context drift / metadata updates).
Reviewed changes
Copilot reviewed 3 out of 4 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| scripts/charon-patch.diff | Updates the patch file metadata/context so git apply continues to work against the new Charon sources. |
| kani-compiler/src/codegen_aeneas_llbc/mir_to_ullbc/mod.rs | Switches tuple arity computation to elem_count() to match Charon v0.1.69’s Vector API. |
| Cargo.lock | Bumps the resolved charon package version to 0.1.69. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
github-merge-queue
Bot
removed this pull request from the merge queue due to failed status checks
Jul 21, 2026
github-merge-queue
Bot
removed this pull request from the merge queue due to failed status checks
Jul 21, 2026
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.
Advance the Charon pin from v0.1.68 (63f7749d) to v0.1.69 (485bd36e), the next step of the incremental effort to catch the pinned Charon up with upstream (the endgame is dropping scripts/charon-patch.diff entirely).
Charon v0.1.69 makes
Vector::elem_countthe way to obtain the number of non-empty slots (lenis removed); adapt the tuple-field-projection translation in the LLBC backend accordingly.Refresh scripts/charon-patch.diff so its hunks apply against the v0.1.69 sources (context-line drift only; the patch content is unchanged).
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 and MIT licenses.