{"id":276,"date":"2007-01-16T20:36:52","date_gmt":"2007-01-16T20:36:52","guid":{"rendered":"http:\/\/scientopia.org\/blogs\/goodmath\/2007\/01\/16\/haskell-the-basics-of-type-classes\/"},"modified":"2007-01-16T20:36:52","modified_gmt":"2007-01-16T20:36:52","slug":"haskell-the-basics-of-type-classes","status":"publish","type":"post","link":"http:\/\/www.goodmath.org\/blog\/2007\/01\/16\/haskell-the-basics-of-type-classes\/","title":{"rendered":"Haskell: the Basics of Type Classes"},"content":{"rendered":"

One thing that we’ve seen already in Haskell programs is type
\nclasses<\/em>. Today, we’re going to try to take our first look real look
\nat them in detail – both how to use<\/em> them, and how to define<\/em> them. This still isn’t the entire picture around type-classes; we’ll come back for another look at them later. But this is a beginning – enough to
\nreally understand how to use them in basic Haskell programs, and enough to give us the background we’ll need to attack Monads, which are the next big topic.<\/p>\n

Type classes are Haskell’s mechanism for managing parametric polymorphism. Parametric polymorphism
\nis a big fancy term for code that works with type parameters. The idea of type classes is to provide a
\nmechanism for building constrained<\/em> polymorphic functions: that is, functions whose type involves a type parameter, but which needs some constraint to limit<\/em> the types that can be used to instantiate it, to specify what properties its type parameter must have. In essence, it’s doing very much the same thing that parameter type declarations let us do for the code. Type declarations let us say “the value of this parameter can’t be just any value – it must be a value which is a member of this particular type”; type-class declarations let us say “the type parameter for instantiating this function can’t be just any type – it must be a type which is a member of this type-class.”<\/p>\n

<\/p>\n

The type declarations in Haskell let us do this in a very flexible way, derived from something called the Curry-Howard isomorphism, which shows that type systems for lambda calculus are isomorphic to inference systems in some logic. The simply-typed lambda calculus has a type system related to simple propositional logic; Haskell, with its type variables, has a type system derived from first order predicate logic. <\/p>\n

In fact, in Haskell, when you declare a type with a type variable, in the logic of the type
\nsystem, you’ve implicitly quantified the type with a universal quantifier. So a type “a -> b” in
\nHaskell is actually implicitly understood to mean: (∀ a,b : a → b). <\/p>\n

If you think back to predicate logic, you might recall that “such that” constructions like “∀ x such that x ∈ S: T(x) → U(x)” are not really primitives in the logic – they’re just a shorthand for a logical implication: ∀ x : (x ∈ T) → (T(x) → U(x)). That’s exactly what Haskell does with type-classes – it writes that as predicate (e.g., “Num(x)<\/code>) with an implication symbol (“=><\/code>“). The reason for the separate implication symbol is
\nbasically just to visually distinguish the part of the type that is a constraint on the type variables. So when you write something like “(Eq a) => a -> a -> Bool<\/code>“, what your really saying is “For all types a such that a is in Eq, this function has type “a -> a -> Bool”.<\/p>\n

Enough theory – let’s look at how we really use these things. Suppose we wanted to write a function
\nthat added a list of values. Without using type classes, you might try to write it as:<\/p>\n

\naddValues :: [a] -> a\naddValues v:vs = v + (addValues vs)\naddValues v:[] = v\n<\/pre>\n
 If you were to try to compile that function, you’d get a compile error: it uses the “+” operation on values of type a, but the type declaration says that it works on any<\/em> type a. What we need to do is specify a type constraint that supports addition – like Num<\/code>:<\/p>\n
\n>addValues :: Num a => [a] -> a\n>addValues (v:[]) = v\n>addValues (v:vs) = v + (addValues vs)\n<\/pre>\n
 What we’ve done is chosen the appropriate type predicate for selecting types that we can use in the function. And there’s something important about that: the Haskell prelude and standard libraries define a lot<\/em> of type classes. If you’re not defining a type-class for something very specific to your application, there’s a good chance that there’s already a suitable type-class in the libraries, and you should use the library one, rather than defining your own. Your code will be much<\/em> more portable and reusable if you take advantage of the type classes in the standard libraries.<\/p>\n
 Whether you’re only going to use library classes, or define your own, you’ll still need to be able to read type-class declarations, and read and write instances. <\/p>\n
 A type-class declaration consists of two basic parts: the first is a declaration of what operations (methods) an instance of the class must support; and the second is a set of default implementations of those methods.<\/p>\n
 For example here’s the declaration for the type-class Ord<\/code>, which is the class of all
\nordered types:<\/p>\n
\nclass (Eq a) => Ord a where\ncompare              :: a -> a -> Ordering\n(<), (<=), (>=), (>) :: a -> a -> Bool\nmax, min             :: a -> a -> a\ncompare x y | x == y    = EQ\n| x <= y    = LT\n| otherwise = GT\nx <= y  = compare x y \/= GT\nx <  y  = compare x y == LT\nx >= y  = compare x y \/= LT\nx >  y  = compare x y == GT\n-- Note that (min x y, max x y) = (x,y) or (y,x)\nmax x y | x <= y    =  y\n| otherwise =  x\nmin x y | x <= y    =  x\n| otherwise =  y\n<\/pre>\n
 The first line declares the name of the class being declared, and any constraints on what types can be instances of this class. The constraints are other type classes that a type must be an instance of before it can be made an instance of the new type. In the case of Ord<\/code>, it says
\n\"(Eq a) => Ord a\"<\/code>, which means before a type can be an instance of Ord<\/code>,
\nit must also be an instance of Eq<\/code>. The type variable a<\/code> will be used throughout the class definition to refer to an instance of type-class Ord<\/code>. <\/p>\n
 After the declaration line, there are a list of function-type declarations. These declare the
\nmethods<\/em> that must be implemented in order to be an instance of the class. (We’ll get to how
\nfunctions are made into type-class methods when we look at the instance declarations.)<\/p>\n
 What this says is: for a type to be an instance of Ord<\/code>, it must first be an instance of Eq<\/code>; and to be an instance of Ord<\/code>, it needs to provide implementations
\nof methods for compare<\/code>, <<\/code>, <=<\/code>, ><\/code>, >=<\/code>, max<\/code>, and min<\/code>. It then provides some default implementations – if an instance declaration doesn’t specify an implementation of a method for its type, then the default from the class declaration will be used. There’s one interesting thing to note about the default methods: a default method can use any operation specified on the type-class, or required by the class constraint. The default methods do not<\/em> have to make sense together. If you were to use Ord<\/code> without providing an implementation of either <=<\/code> or compare<\/code>, you’d wind up the Ord<\/code> operations all being infinite loops! The default implementation of compare<\/code> is written in terms of <=<\/code>; and the default implementation of <=<\/code> is written in terms of compare<\/code>.<\/p>\n
 So what would a type-instance of class Ord<\/code>  look like? Let’s try putting together the beginnings of an implementation of surreal numbers.<\/a>.<\/p>\n
\n>-- A surreal number is a number with two sets of surreals:\n>--    a left set which contains elements less than it, and\n>--    a right set which contains elements greater than it.\n>-- By definition, zero is the surreal with both sets empty.\n>\n>data Surreal = Surreal [Surreal] [Surreal] deriving (Eq, Show)\n>srZero = Surreal [] []\n>srPlusOne = Surreal [srZero] []\n>srMinusOne = Surreal [] [srZero]\n>srPlusOneHalf = Surreal [srZero] [srPlusOne]\n<\/pre>\n
 Then, we implement the basic ordering operations on surreal numbers. We don’t do anything special – just implement them as perfectly normal functions. As a reminder, here’s the definition of ≤ for surreal numbers:<\/p>\n
Given two surreal numbers x = {XL<\/sub>|XR<\/sub>} and y = {YL<\/sub>|YR<\/sub>}, x ≤ y if and only if:<\/p>\n
    \n
  1.  ¬∃xi<\/sub>∈XL<\/sub> : y ≤ xi<\/sub>, and<\/li>\n
  2.  ¬∃yi<\/sub>∈YR<\/sub> : yi<\/sub> ≤ x<\/li>\n<\/ol>\n
    \n>srleq :: Surreal -> Surreal -> Bool\n>srleq x@(Surreal [] []) y@(Surreal [] []) = True\n>srleq x@(Surreal xl xr) y@(Surreal yl yr) =\n>      (all (yi -> not (srleq yi x))  yr) &&\n>      (all (xi -> not (srleq y xi)) xl)\n<\/pre>\n
     Now, we can bind these functions into the type-class class method,
    \nso that they’ll be used for surreal numbers:<\/p>\n
    \n>instance Ord (Surreal) where\n>   x <= y  = srleq x y\n<\/pre>\n
     The where<\/code> clause of the instance declaration contains
    \na perfectly normal list of function declarations. The only reason for separating the function declarations from the instance declaration is
    \nbecause it allowed us to write the type declaration, and it made the
    \ncode clearer to have a separate declaration of the ≤ operation (with the explanation of what ≤ means for surreal numbers) than it would have to
    \nput the implementation in-line.<\/p>\n
     With that declaration, we can now use all<\/em> of the comparison operations defined in Ord<\/code> on our surreal numbers:<\/p>\n
    \n*Main> srZero <= srPlusOne\nTrue\n*Main> srZero <= srMinusOne\nFalse\n*Main> srPlusOneHalf > srZero\nTrue\n*Main> srPlusOneHalf  srMinusOne <= srZero\nTrue\n*Main> compare srZero srMinusOne\nGT\n*Main>\n<\/pre>\n","protected":false},"excerpt":{"rendered":"
    One thing that we’ve seen already in Haskell programs is type classes. Today, we’re going to try to take our first look real look at them in detail – both how to use them, and how to define them. This still isn’t the entire picture around type-classes; we’ll come back for another look at them […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"jetpack_post_was_ever_published":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":false,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":false},"version":2}},"categories":[89],"tags":[],"class_list":["post-276","post","type-post","status-publish","format-standard","hentry","category-haskell"],"jetpack_publicize_connections":[],"jetpack_featured_media_url":"","jetpack_shortlink":"https:\/\/wp.me\/p4lzZS-4s","jetpack_sharing_enabled":true,"jetpack_likes_enabled":true,"_links":{"self":[{"href":"http:\/\/www.goodmath.org\/blog\/wp-json\/wp\/v2\/posts\/276","targetHints":{"allow":["GET"]}}],"collection":[{"href":"http:\/\/www.goodmath.org\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/www.goodmath.org\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/www.goodmath.org\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/www.goodmath.org\/blog\/wp-json\/wp\/v2\/comments?post=276"}],"version-history":[{"count":0,"href":"http:\/\/www.goodmath.org\/blog\/wp-json\/wp\/v2\/posts\/276\/revisions"}],"wp:attachment":[{"href":"http:\/\/www.goodmath.org\/blog\/wp-json\/wp\/v2\/media?parent=276"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/www.goodmath.org\/blog\/wp-json\/wp\/v2\/categories?post=276"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/www.goodmath.org\/blog\/wp-json\/wp\/v2\/tags?post=276"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}