Demo Data from VLDB 2026 / reviewers in the wild / expert
Olek Gierczak
dblp:380/9723
· DBLP profile ↗
2ranked-venue papers
1as first author
2since 2021 · last 2025
0009-0002-8850-0984ORCID · corroborated
Domains — the database's venue-derived domains; a paper can count in several
Software engineering, systems software and programming languages · 2 · 1 first-author · 2 since 2021
Expertise — from the expertise taxonomy: the topics of the expert's papers under the CCF categories. A weight counts papers with recency: 1 for a paper about the topic, 0.3 when the topic is its context, halved every five years.
| Software engineering, system software, and programming languages
2 papers |
Programming languages and type systems · 96% Program verification · 4% |
Topics — the 7 heaviest of 7, each with the papers that count most for it
| Topic | Weight | Papers | Last | Evidence papers |
|---|---|---|---|---|
Programming languages and type systems › type systems
type soundness |
1.6 | 2 | 2025 | From Linearity to Borrowing · Proc. ACM Program. Lang. 2025 Gradually Typed Languages Should Be Vigilant! · Proc. ACM Program. Lang. 2024 |
Programming languages and type systems › type systems › ownership types
borrowing |
0.9 | 1 | 2025 | From Linearity to Borrowing · Proc. ACM Program. Lang. 2025 |
Programming languages and type systems › type systems › substructural type systems
linear types |
0.9 | 1 | 2025 | From Linearity to Borrowing · Proc. ACM Program. Lang. 2025 |
Programming languages and type systems › type systems
gradual typing |
0.8 | 1 | 2024 | Gradually Typed Languages Should Be Vigilant! · Proc. ACM Program. Lang. 2024 |
Programming languages and type systems › type checking
runtime type checking |
0.8 | 1 | 2024 | Gradually Typed Languages Should Be Vigilant! · Proc. ACM Program. Lang. 2024 |
Programming languages and type systems
type systems |
0.8 | 1 | 2024 | Gradually Typed Languages Should Be Vigilant! · Proc. ACM Program. Lang. 2024 |
Program verification › program logic
separation logic |
0.3 | 1 | 2025 | From Linearity to Borrowing · Proc. ACM Program. Lang. 2025 |
Methods — techniques the papers use, named apart from their topics
separation logic · 0.9semantic model · 0.9vigilance · 0.8semantic analysis · 0.8
| Year | Publication | Venue | Position |
|---|---|---|---|
| 2025 | From Linearity to BorrowingabstractLinear type systems are powerful because they can statically ensure the correct management of resources like memory, but they can also be cumbersome to work with, since even benign uses of a resource require that it be explicitly threaded through during computation. Borrowing , as popularized by Rust, reduces this burden by allowing one to temporarily disable certain resource permissions (e.g., deallocation or mutation) in exchange for enabling certain structural permissions (e.g., weakening or contraction). In particular, this mechanism spares the borrower of a resource from having to explicitly return it to the lender but nevertheless ensures that the lender eventually reclaims ownership of the resource. In this paper, we elucidate the semantics of borrowing by starting with a standard linear type system for ensuring safe manual memory management in an untyped lambda calculus and gradually augmenting it with immutable borrows, lexical lifetimes, reborrowing, and finally mutable borrows. We prove semantic type soundness for our Borrow Calculus ( BoCa ) using Borrow Logic ( BoLo ), a novel domain-specific separation logic for borrowing. We establish the soundness of this logic using a semantic model that additionally guarantees that our calculus is terminating and free of memory leaks. We also show that our Borrow Logic is robust enough to establish the semantic safety of some syntactically ill-typed programs that temporarily break but reestablish invariants. Andrew Wagner, Olek Gierczak, Brianna Marshall, John M. Li, Amal Ahmed 0001 |
Proc. ACM Program. Lang. | 2 |
| 2024 | Gradually Typed Languages Should Be Vigilant!abstractIn gradual typing, different languages perform different dynamic type checks for the same program even though the languages have the same static type system. This raises the question of whether, given a gradually typed language, the combination of the translation that injects checks in well-typed terms and the dynamic semantics that determines their behavior sufficiently enforce the static type system of the language. Neither type soundness, nor complete monitoring, nor any other meta-theoretic property of gradually typed languages to date provides a satisfying answer. In response, we present vigilance, a semantic analytical instrument that defines when the check-injecting translation and dynamic semantics of a gradually typed language are adequate for its static type system. Technically, vigilance asks if a given translation-and-semantics combination enforces the complete run-time typing history of a value, which consists of all of the types associated with the value. We show that the standard combination for so-called Natural gradual typing is vigilant for the standard simple type system, but the standard combination for Transient gradual typing is not. At the same time, the standard combination for Transient is vigilant for a tag type system but the standard combination for Natural is not. Hence, we clarify the comparative type-level reasoning power between the two most studied approaches to sound gradual typing. Furthermore, as an exercise that demonstrates how vigilance can guide design, we introduce and examine a new theoretical static gradual type system, dubbed truer, that is stronger than tag typing and more faithfully reflects the type-level reasoning power that the dynamic semantics of Transient gradual typing can guarantee. Olek Gierczak, Lucy Menon, Christos Dimoulas, Amal Ahmed 0001 |
Proc. ACM Program. Lang. | 1 |