From: simonmar Date: Mon, 3 Nov 2003 17:26:04 +0000 (+0000) Subject: [project @ 2003-11-03 17:26:04 by simonmar] X-Git-Tag: Approx_11550_changesets_converted~281 X-Git-Url: http://git.megacz.com/?a=commitdiff_plain;h=ed53c6775a6b81509fc8955d066ee7d0197eb29c;hp=0b2c6f7cb6a15bfcc32e3ca729a10a47d9d21be1;p=ghc-hetmet.git [project @ 2003-11-03 17:26:04 by simonmar] Remove references to non-existent g3 function. --- diff --git a/ghc/docs/users_guide/glasgow_exts.sgml b/ghc/docs/users_guide/glasgow_exts.sgml index 5280bcd..af0a768 100644 --- a/ghc/docs/users_guide/glasgow_exts.sgml +++ b/ghc/docs/users_guide/glasgow_exts.sgml @@ -2296,8 +2296,8 @@ the forall is on the left of a function arrrow. As shows, the polymorphic type on the left of the function arrow can be overloaded. -The functions f3 and g3 have rank-3 types; -they have rank-2 types on the left of a function arrow. +The function f3 has a rank-3 type; +it has rank-2 types on the left of a function arrow. GHC allows types of arbitrary rank; you can nest foralls @@ -2309,7 +2309,7 @@ including an operational type class context, is legal: On the left of a function arrow On the right of a function arrow (see ) As the argument of a constructor, or type of a field, in a data type declaration. For -example, any of the f1,f2,f3,g1,g2,g3 above would be valid +example, any of the f1,f2,f3,g1,g2 above would be valid field type signatures. As the type of an implicit parameter In a pattern type signature (see )