Changes between Version 16 and Version 17 of Records/DeclaredOverloadedRecordFields

Timestamp:

03/02/12 20:29:29 (15 months ago)

Author:

AntC

Comment:

correct an export list

Records/DeclaredOverloadedRecordFields

@@ -150 +150 @@
 {{{
 {-# OPTIONS_GHC -XDeclaredOverloadedRecordFields             #-}
-module M( x )       where
+module M( x, T )       where
     fieldLabel x,y :: r -> Int
     data T = MkT { x, y :: Int }
 }}}
-Here only the field selector function `x` is exported. The representation is abstract, the client can't construct or dismantle a record type `T`;
+Here only the field selector function `x` and type `T` are exported. The representation is abstract, the client can't construct or dismantle a record type `T`;
 
   The existence of field `y` is hidden altogether.
@@ -168 +168 @@
 then you are exporting the `x` field within record type `T`, but __not__ the field selector `x` (nor the generated type 'peg' `Proxy_x`).
 
-Type `T` and field label `x` are exported, but not data constructor `MkT`, so `x` is (almost) unusable. (It can be used to update an existing record (without changing its record constructor) using syntax: `r{ x = 57 }`.)
+Type `T` and field label `x` are exported, but not data constructor `MkT`, so `x` is unusable. (It can't even be used to update an existing record using syntax: `r{ x = 57 }`, because that syntax now has a different semantics.)
 
   The existence of field `y` is hidden altogether.