UP | HOME

list : Types

Navigation   notoc

Motivations

Examples

Types   notoc nav

Types   notoc

Maybe null done right

  • Handle optional values without guessing and without exceptions
  • Maintain type invariants in smart constructors

Valid validate once, retain proof

  • Validate a value once and once only
  • Have type-level proof that a value has been validated with a specific validator
  • Statically guarantee that invalid results are handled

Eff track and restrict effects

  • Track effects in types
  • Interleave different types of effects
  • Restrict sections of code to a set of effects

Type constructors higher kinded abstraction

  • Allow more general abstraction
  • Reduce repetition

Monads

  • Restrict evaluation to a type constructor context
  • The type constructor determines the semantics of the evaluation