VLDB 2026 Research / reviewers in the wild / expert
Sam Lasser
dblp:248/3439
· DBLP profile ↗
3ranked-venue papers
2as first author
2since 2021 · last 2022
—ORCID · none
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 2021Theory of computation · 2 · 1 first-author · 1 since 2021
| Year | Publication | Venue | Position |
|---|---|---|---|
| 2022 | Verbatim++: verified, optimized, and semantically rich lexing with derivativesabstractLexers and parsers are attractive targets for attackers because they often sit at the boundary between a software system's internals and the outside world. Formally verified lexers can reduce the attack surface of these systems, thus making them more secure. Derek Egolf, Sam Lasser, Kathleen Fisher |
CPP | 2 |
| 2021 | CoStar: a verified ALL(*) parserabstractParsers are security-critical components of many software systems, and verified parsing therefore has a key role to play in secure software design. However, existing verified parsers for context-free grammars are limited in their expressiveness, termination properties, or performance characteristics. They are only compatible with a restricted class of grammars, they are not guaranteed to terminate on all inputs, or they are not designed to be performant on grammars for real-world programming languages and data formats. Sam Lasser, Chris Casinghino, Kathleen Fisher, Cody Roux |
PLDI | 1 |
| 2019 | A Verified LL(1) Parser GeneratorabstractAn LL(1) parser is a recursive descent algorithm that uses a single token of lookahead to build a grammatical derivation for an input sequence. We present an LL(1) parser generator that, when applied to grammar G, produces an LL(1) parser for G if such a parser exists. We use the Coq Proof Assistant to verify that the generator and the parsers that it produces are sound and complete, and that they terminate on all inputs without using fuel parameters. As a case study, we extract the tool’s source code and use it to generate a JSON parser. The generated parser runs in linear time; it is two to four times slower than an unverified parser for the same grammar. Sam Lasser, Chris Casinghino, Kathleen Fisher, Cody Roux |
ITP | 1 |