Difference between revisions of "Hask"
(→Hask is not Cartesian closed: strict product) 
Benmachine (talk  contribs) (id is a function :)) 

(5 intermediate revisions by one other user not shown)  
Line 1:  Line 1:  
−  '''Hask''' refers to a [[Category theorycategory]] with types as objects and functions between them as morphisms. However, its use is ambiguous. Sometimes it refers to Haskell (''actual '''Hask'''''), and sometimes it refers to some subset of Haskell where no values are bottom and all functions terminate (''platonic '''Hask'''''). The reason for this is that platonic '''Hask''' has lots of nice properties that actual '''Hask''' does not, and is thus easier to reason in. There is a faithful functor from platonic '''Hask''' to actual '''Hask''' allowing programmers to think in the former to write code in the latter. 

+  '''Hask''' is the [[Category theorycategory]] of Haskell types and functions. 

−  == Definition == 

⚫  The objects of '''Hask''' are Haskell types, and the morphisms from objects <hask>A</hask> to <hask>B</hask> are Haskell functions of type <hask>A > B</hask>. The identity morphism for object <hask>A</hask> is <hask>id :: A > A</hask>, and the composition of morphisms <hask>f</hask> and <hask>g</hask> is <hask>f . g = \x > f (g x)</hask>. 

−  
⚫  The objects of '''Hask''' are Haskell types, and the morphisms from objects <hask>A</hask> to <hask>B</hask> are Haskell functions of type <hask>A > B</hask>. The identity morphism for object <hask>A</hask> is <hask>id :: A</hask>, and the composition of morphisms <hask>f</hask> and <hask>g</hask> is <hask>f . g = \x > f (g x)</hask>. 

== Is '''Hask''' even a category? == 
== Is '''Hask''' even a category? == 

Line 41:  Line 39:  
 <hask>data Either a b 
 <hask>data Either a b 

= Left a  Right b</hask> 
= Left a  Right b</hask> 

−   <hask>data (a,b) = 
+   <hask>data (a,b) = 
−  +  (,) { fst :: a, snd :: b}</hask> 

+   <hask>data P a b = 

+  P {fstP :: !a, sndP :: !b}</hask> 

 
 

! scope="row"  Requirement 
! scope="row"  Requirement 

Line 80:  Line 78:  
<br /><hask>sndP . u = g</hask> 
<br /><hask>sndP . u = g</hask> 

 
 

−  ! scope="row"  
+  ! scope="row"  Candidate 
 <hask>u1 r = case r of {}</hask> 
 <hask>u1 r = case r of {}</hask> 

 <hask>u1 _ = ()</hask> 
 <hask>u1 _ = ()</hask> 

Line 98:  Line 96:  
<br /><hask>g _ = undefined</hask> 
<br /><hask>g _ = undefined</hask> 

 <hask>r ~ ()</hask> 
 <hask>r ~ ()</hask> 

−  <br /><hask>f _ = 
+  <br /><hask>f _ = ()</hask> 
−  <br /><hask>g _ = 
+  <br /><hask>g _ = undefined</hask> 
 
 

! scope="row"  Alternative u 
! scope="row"  Alternative u 

Line 117:  Line 115:  
 <hask>u1 _ = (undefined,undefined)</hask> 
 <hask>u1 _ = (undefined,undefined)</hask> 

<br /><hask>u2 _ = undefined</hask> 
<br /><hask>u2 _ = undefined</hask> 

−   <hask> 
+   <hask>f _ = ()</hask> 
−  <br /><hask>(fstP 
+  <br /><hask>(fstP . u1) _ = undefined</hask> 
 style="background: red;" 
 style="background: red;" 

! scope="row"  Result 
! scope="row"  Result 

Line 130:  Line 128:  
== "Platonic" '''Hask''' == 
== "Platonic" '''Hask''' == 

−  Because of these difficulties, Haskell developers tend to think in some subset of Haskell where types do not have bottom values. This means that it only includes functions that terminate, and typically only finite values. The corresponding category has the expected initial and terminal objects, sums and products 
+  Because of these difficulties, Haskell developers tend to think in some subset of Haskell where types do not have bottom values. This means that it only includes functions that terminate, and typically only finite values. The corresponding category has the expected initial and terminal objects, sums and products, and instances of Functor and Monad really are endofunctors and monads. 
== Links == 
== Links == 
Latest revision as of 20:35, 13 September 2012
Hask is the category of Haskell types and functions.
The objects of Hask are Haskell types, and the morphisms from objects A
to B
are Haskell functions of type A > B
. The identity morphism for object A
is id :: A > A
, and the composition of morphisms f
and g
is f . g = \x > f (g x)
.
Is Hask even a category?
Consider:
undef1 = undefined :: a > b
undef2 = \_ > undefined
Note that these are not the same value:
seq undef1 () = undefined
seq undef2 () = ()
This might be a problem, because undef1 . id = undef2
. In order to make Hask a category, we define two functions f
and g
as the same morphism if f x = g x
for all x
. Thus undef1
and undef2
are different values, but the same morphism in Hask.
Hask is not Cartesian closed
Actual Hask does not have sums, products, or an initial object, and ()
is not a terminal object. The Monad identities fail for almost all instances of the Monad class.
Initial Object  Terminal Object  Sum  Product  Product  

Type  data Empty

data () = ()

data Either a b = Left a  Right b

data (a,b) = (,) { fst :: a, snd :: b}

data P a b = P {fstP :: !a, sndP :: !b}

Requirement  There is a unique function

There is a unique function

For any functions
there is a unique function
such that:

For any functions
there is a unique function
such that:

For any functions
there is a unique function
such that:

Candidate  u1 r = case r of {}

u1 _ = ()

u1 (Left a) = f a

u1 r = (f r,g r)

u1 r = P (f r) (g r)

Example failure condition  r ~ ()

r ~ ()

r ~ ()

r ~ ()

r ~ ()

Alternative u  u2 _ = ()

u2 _ = undefined

u2 _ = ()

u2 _ = undefined


Difference  u1 undefined = undefined

u1 _ = ()

u1 undefined = undefined

u1 _ = (undefined,undefined)

f _ = ()

Result  FAIL  FAIL  FAIL  FAIL  FAIL 
"Platonic" Hask
Because of these difficulties, Haskell developers tend to think in some subset of Haskell where types do not have bottom values. This means that it only includes functions that terminate, and typically only finite values. The corresponding category has the expected initial and terminal objects, sums and products, and instances of Functor and Monad really are endofunctors and monads.