Papers › Tracking Captured Variables in Types

Tracking Captured Variables in Types

25 May 2021arXiv:2105.11896links table onlyarchive 2025-07-28

Aleksander Boruch-Gruszecki, Jonathan Immanuel Brachthäuser, Edward Lee, Ondřej Lhoták, Martin Odersky

The archive published only this paper's code-link row. Authors, date and abstract are from arXiv's metadata (CC0), read from the Kaggle arXiv metadata snapshot of 2026-09-12 where its title matched the archive's; the title is the archive's.

Type systems usually characterize the shape of values but not their free variables. However, there are many desirable safety properties one could guarantee if one could track how references can escape. For example, one may implement algebraic effect handlers using capabilities -- a value which permits one to perform the effect -- safely if one can guarantee that the capability itself does not escape the scope bound by the effect handler. To this end, we study the CF_(<:) calculus, a conservative and lightweight extension of System F_(<:), to track how values and their references can be captured and escape. We show that existing terms in System F_(<:) embed naturally in our calculus, and that many natural problems can be expressed in a system that tracks variable references like we do in CF_(<:). We also give mechanized proofs of the soundness properties of CF_(<:) in Coq. The type system presented in CF_(<:) is powerful enough to reason about safety in the context of many natural extensions of CF_(<:) such as region-based memory-management, non-local returns, and effect handlers.

PaperPDFCode

Code

tiarkrompf/reachability mentioned on GitHub report

Repository list and official/mentioned flags are the archive's, frozen 2025-07-28. Reachability, where shown, is from one Syntology probe window (2026-09-16 to 2026-09-18); repositories not probed show nothing. GitHub stars are not tracked.

Code Syntology ran Syntology

Not run by Syntology. Nothing on this page verifies that the listed code works.

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

Report a problem or propose a change · a person checks every report against the paper or source before anything changes; decisions are listed on /corrections