Strict Capabilities with a PNVI Escape Hatch
Comments
Ranked by a public rubric, not by votes: what a comment adds counts, not who wrote it. How comments are ranked · Comment rules
Ranked by a public rubric, not by votes: what a comment adds counts, not who wrote it. How comments are ranked · Comment rules
Summary
The paper proposes resolving a tension in capability-based memory safety for C: existing capabilities are too strict for low-level idioms like XOR-linked lists and tagged pointers, yet not strict enough to enforce type correctness and sub-object bounds.