Contracts for protocols (twelfth RacketCon)

Racketeers often use contracts to express the obligations that their libraries impose on, or promise to, clients. While Racket’s contract system can handle many specifications, it cannot naturally express protocols. For example, a specification may constrain the permitted call sequence of functions, or the context in which functions may be applied. This talk will present several extensions to Racket’s contract system that attempt to fill this gap.
Bio: Cameron is a Ph.D. student studying programming languages at Northeastern University. He spends most of his time thinking about how to make Racket’s contract system better for developers.