Changes between Version 11 and Version 12 of Records/DeclaredOverloadedRecordFields/COmpareSORF

Timestamp:

02/21/12 14:13:44 (15 months ago)

Author:

guest

Comment:

--

Records/DeclaredOverloadedRecordFields/COmpareSORF

@@ -56 +56 @@
 Did that just re-open the back door to the abstraction?
 {{{
-       e { x = True } ===> set (undefined ::: "x") True e       -- desugarred
+       e{ x = True } ===> set (undefined ::: "x") True e       -- desugarred
 }}}
     ?I didn't need `e`'s record type in scope nor its field `x` to call `set`.
@@ -62 +62 @@
     So I can break the abstraction by updating a record/field I can't even `get` ??
 
-    Also, without the signature for `customer_id`, I don't know its result type. So I can't efficitently generate type instances for `GetResult`. (That is, I'd generate a type instance for each record type it appears in, with every one returning result `Int`.)
+    Also, without the signature for `customer_id`, I don't know its result type. So I can't cleanly generate type instances for `GetResult`. (That is, I'd generate a type instance for each record type it appears in, with every one returning result `Int`.)