This is an ACM-published paper (ICFP 2024, based on the DOI) describing Jane Street's ongoing work to graft Rust-style memory management onto OCaml — without breaking the language's existing semantics or ecosystem. The title's "modal" is the key technical hook: rather than introducing a full borrow checker or affine type system as separate machinery, the authors extend OCaml's type system with modes — orthogonal annotations layered on top of existing types that track properties like uniqueness, locality (stack vs. heap), and linearity.

Why this matters for a technical audience:

• It's a real-world experiment at scale. Jane Street runs one of the largest OCaml codebases in industry. Any language extension they publish has been battle-tested against millions of lines of production trading code, not just toy benchmarks.
• Modes are a genuinely novel design point. Most attempts to add ownership to a garbage-collected language either bolt on a separate sublanguage (like Scala's capture checking) or require rewrites. Modes let existing code keep working while new code opts into stricter guarantees — a gradual-typing story for memory management.
• It bridges two research traditions. ML-family type theory and substructural type systems (linear/affine logic, à la Rust) have historically evolved separately. This work shows how to unify them without the usual tradeoffs.
• Performance implications are concrete. Stack allocation, avoiding GC pressure on hot paths, and safe in-place mutation are the kinds of wins that matter for latency-sensitive systems — exactly Jane Street's domain.

The paper is also a good read for anyone thinking about language evolution more broadly. Adding a feature this fundamental to a mature language is usually a decade-long saga (see: Python's type hints, Java's value types). OCaml's willingness to experiment here — and Jane Street's willingness to fork and upstream — is a case study in how industrial users can drive research-grade language design.

The fact that this sits at 1 point with zero comments is a shame. It's exactly the kind of PL-research-meets-production-engineering content that HN's audience usually devours when it surfaces.