Liquid Types are a tool that enriches existing type systems by allowing programmers to specify and verify semantic properties of their code. Unlike traditional type systems that reason about the structure of program values, Liquid Types also consider the semantics of values. This means that Liquid Types can statically catch semantic type errors, such as division by zero. By providing specifications for operators like the divisor operator, Liquid Types ensure that the code satisfies the specifications, preventing runtime exceptions. The verification process involves subtyping queries and implication checking. While Liquid Types offer a powerful way to verify code, there may still be cases where the analysis is not complete or may produce false errors. However, when the system says “OK,” it guarantees that there will be no violation of the specification. Liquid Types were introduced in 2008 and have been used to verify ML, C, and Haskell. They are dependent types that rely on refined logical predicates from a decidable sublanguage, allowing for decidable type checking. Overall, Liquid Types provide a highly automated type system with a low requirement for type annotations.
https://goto.ucsd.edu/~ucsdpl-blog/liquidtypes/2015/09/19/liquid-types/