Skip to content
0:00 / 0:00

#typedclojure#gradualtyping#typesystems

"Typed Clojure: From Optional to Gradual Typing" by Ambrose Bonnaire-Sergeant

Strange Loop Conference

88K subscribers • 114 videos on Hallway • Conference channel

YouTube
  • Recommended by 1 person: 1 in engineering communities.
  • Presented by Ambrose Bonnaire-Sergeant, PhD student at Indiana University Bloomington

Intermediate. Assumes working knowledge.

3.7K views11 years ago1 recommendation

Programming languagesLisp and ClojureLanguage design and type systems

Ambrose Bonnaire-Sergeant presents extensions to Typed Clojure that transition it from an optional to a gradual typing system.

Optional type systems enable type checking for otherwise untyped languages, but what happens when you need to interact with untyped libraries? In most systems, the user provides an unchecked annotation which the type system assumes correct. An incorrect annotation then compromises all guarantees of the type system. Gradual typing addresses this by inserting dynamic checks that protect the static invariants of typed code. In this talk we present extensions to Typed Clojure promoting it from an Optional to a Gradual typing system. Ambrose Bonnaire-Sergeant INDIANA UNIVERSITY BLOOMINGTON @ambrosebs Ambrose is a Computer Science PhD student at Indiana University Bloomington, working on gradual typing and Typed Clojure.

Why it's here

1 person recommends this

u/zarandysofiain r/Clojure • Recommends

"Typed Clojure: From Optional to Gradual Typing" by Ambrose Bonnaire-Sergeant (Strange Loop 2015)

u/gcornutin r/Clojure • Mentions

On “"A Dynamic, Statically Typed Contradiction" by Andrew Mcveigh”

Core.typed will soon provide a similar type inference or automatically generated type annotations (with compatibility with clojure spec): http://ambrosebs.com/auto-ann.html Also the author of core typed wants to move from an optional type system to a gradual type system (where you could use un-typped code with typed code and vice-versa): [video