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

Store the type of each place #457

Merged
merged 4 commits into from
Nov 18, 2024
Merged

Conversation

Nadrieril
Copy link
Member

@Nadrieril Nadrieril commented Nov 7, 2024

This changes the representation of places to be recursive instead of using a list of projections. This makes it possible to store the type of each subplace. While I was at it I also improved the API for locals, so we don't need to manipulate Vectors by hand for simple local manipulation.

@Nadrieril Nadrieril force-pushed the types-in-places branch 3 times, most recently from 1ac1c1c to ccd82ed Compare November 12, 2024 16:25
@Nadrieril Nadrieril merged commit 826c269 into AeneasVerif:main Nov 18, 2024
3 of 5 checks passed
@Nadrieril Nadrieril deleted the types-in-places branch November 18, 2024 09:40
github-merge-queue bot pushed a commit to model-checking/kani that referenced this pull request Jan 3, 2025
Update Charon submodule to
AeneasVerif/charon@adc0a85

Relevant Charon PRs:
AeneasVerif/charon#457: This required updating
the code that creates places to also pass in the type.
AeneasVerif/charon#464: This replaced the
file-to-id hash table by a vector, thus requiring that we add one in
Kani's translation context.
AeneasVerif/charon#474: The translation context
is no longer parameterized by a lifetime
AeneasVerif/charon#491: This required changing
the type of indices

By submitting this pull request, I confirm that my contribution is made
under the terms of the Apache 2.0 and MIT licenses.

---------

Co-authored-by: thanhnguyen-aws <ntson@amazon.com>
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.

2 participants