Skip to content

Rust claims article: what rustc proves, and where the proof stops - #10

Merged
compilersutra merged 1 commit into
mainfrom
feat/rust-claims-reality-check
Aug 16, 2026
Merged

Rust claims article: what rustc proves, and where the proof stops#10
compilersutra merged 1 commit into
mainfrom
feat/rust-claims-reality-check

Conversation

@compilersutra

Copy link
Copy Markdown
Owner

Summary

  • Adds a CompilerSutra article that compiles the same memory bugs on rustc 1.93.1, gcc/g++ 13.3, and clang 18, then draws where the safety proof stops (safe Rust, unsafe, FFI, rustc, LLVM, OS).
  • Default vs opt-in is the thesis: Rust v[i] panics; C++ v[i] / C++23 span[i] do not. vector::at throws; span::at is C++26.
  • Wires /docs/articles/rust-claims-a-reality-check into the article index and Compiler Comparisons sidebar, with links from the Rust vs C++ and rustc-pipeline pieces.

This PR is article-only. It does not include clang-flag explorer changes.

Test plan

  • Open /docs/articles/rust-claims-a-reality-check and skim the TL;DR, results table, three index stories, TOCTOU, checklist, and #25860.
  • Confirm sidebar and related-article links at the top of the page.
  • Confirm ISSTA, Miri, Zellic, CVE, and span::at (C++26) links load.

Made with Cursor

… stops.

Compile the same UAF, OOB, data-race, and TOCTOU programs on rustc 1.93.1, gcc 13.3, and clang 18, and wire the page into Compiler Comparisons.

Co-authored-by: Cursor <cursoragent@cursor.com>
@compilersutra
compilersutra merged commit 7977033 into main Aug 16, 2026
1 check failed
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