Demo Data from SIGIR 2026 / reviewers in the wild / expert
David Kempe 0002
dblp:63/5749-2
· DBLP profile ↗
1ranked-venue papers
0as first author
0since 2021 · last 2016
—ORCID · unresolved
Domains — the database's venue-derived domains; a paper can count in several
Software engineering, systems software and programming languages · 1
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
1 paper |
Programming languages and type systems · 87% Program verification · 13% |
Topics — the 2 heaviest of 3, each with the papers that count most for it
| Topic | Weight | Papers | Last | Evidence papers |
|---|---|---|---|---|
Programming languages and type systems › type systems › refinement types
dependent refinement types |
0.2 | 1 | 2016 | Occurrence typing modulo theories · PLDI 2016 |
Programming languages and type systems › type inference
occurrence typing |
0.2 | 1 | 2016 | Occurrence typing modulo theories · PLDI 2016 |
Methods — techniques the papers use, named apart from their topics
SMT solving · 0.2
| Year | Publication | Venue | Position |
|---|---|---|---|
| 2016 | Occurrence typing modulo theoriesabstractWe present a new type system combining occurrence typing---a technique previously used to type check programs in dynamically-typed languages such as Racket, Clojure, and JavaScript---with dependent refinement types. We demonstrate that the addition of refinement types allows the integration of arbitrary solver-backed reasoning about logical propositions from external theories. By building on occurrence typing, we can add our enriched type system as a natural extension of Typed Racket, reusing its core while increasing its expressiveness. The result is a well-tested type system with a conservative, decidable core in which types may depend on a small but extensible set of program terms. In addition to describing our design, we present the following: a formal model and proof of correctness; a strategy for integrating new theories, with specific examples including linear arithmetic and bitvectors; and an evaluation in the context of the full Typed Racket implementation. Specifically, we take safe vector operations as a case study, examining all vector accesses in a 56,000 line corpus of Typed Racket programs. Our system is able to prove that 50% of these are safe with no new annotations, and with a few annotations and modifications we capture more than 70%. Andrew M. Kent, David Kempe 0002, Sam Tobin-Hochstadt |
PLDI | 2 |