Skip to content

Add Blog for Verifying Raw Pointer Arithmetic Operations #53

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

Merged
merged 24 commits into from
May 26, 2025

Conversation

stogaru
Copy link
Contributor

@stogaru stogaru commented Dec 10, 2024

Issue #: Towards model-checking/verify-rust-std#76

Changes

This blog post talks about verifying safety of code that relies on raw pointer arithmetic, and eventual raw pointer access.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@stogaru stogaru marked this pull request as draft December 10, 2024 02:18
@tautschnig
Copy link
Member

@stogaru Are you still working on this, or should it be considered ready-for-review?

@stogaru
Copy link
Contributor Author

stogaru commented Dec 18, 2024

@tautschnig, It's still a work in progress. We will wrap it by this weekend and turn it in for review.

@stogaru stogaru marked this pull request as ready for review December 22, 2024 22:04
@stogaru
Copy link
Contributor Author

stogaru commented Dec 22, 2024

@tautschnig , the PR is ready for review.

@stogaru
Copy link
Contributor Author

stogaru commented Dec 28, 2024

@feliperodri, FYI

@patricklam
Copy link

I was looking around at other challenges and noticed that this has been languishing around for a while. The blog content itself looks fine to me though I would say more about how kani::mem::same_allocation works (and maybe tighten the prose, but I'm not here to edit text...)

@tautschnig tautschnig merged commit 71599a0 into model-checking:main May 26, 2025
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.

6 participants