Changes between Version 17 and Version 18 of Proposals/transformers

Show
Ignore:
Timestamp:
11/04/10 18:33:46 (4 years ago)
Author:
ross (IP: 81.98.180.212)
Comment:

fix

Legend:

Unmodified
Added
Removed
Modified
  • Proposals/transformers

    v17 v18  
    100100The attached test report lists the packages involved. 
    101101 
    102 === Transition to mtl-2 === 
     102=== Upgrading to mtl-2 === 
    103103Most packages build unchanged with mtl-2.  Most of the remainder require only small changes to upgrade to it, though that will usually render them incompatible with mtl-1 without some CPP directives.  Here are the fixes for common messages: 
    104104 
     
    110110 
    111111''Not in scope: data constructor State'' 
    112  The {{{State}}} type is now a type synonym.  You could replace the {{State}} data constructor with the {{state}} function from {{{Control.Monad.Trans.State}}} in the {{{transformers}}} package. 
     112 The {{{State}}} type is now a type synonym.  You could replace the {{{State}}} data constructor with the {{{state}}} function from {{{Control.Monad.Trans.State}}} in the {{{transformers}}} package. 
    113113 
    114114''Not in scope: runState'' 
    115115 You probably imported {{{State(..)}}}, which won't work now that {{{State}}} is a type synonym.  You need to import {{{State}}} and {{{runState}}}.  (That will work with old versions on mtl too.) 
    116116 
    117 ''Illegal instance declaration for MyClass (State Foo)'' 
    118  If you have a matching instance for {{StateT}}, you can delete this one.  Otherwise you need to generalize your instance to {{StateT}}.  If that's not possible, you may need to introduce a newtype. 
     117''Illegal instance declaration for Myclass (State Foo)'' 
     118 If you have a matching instance for {{{StateT}}}, you can delete this one.  Otherwise you need to generalize your instance to {{{StateT}}}.  If that's not possible, you may need to introduce a newtype. 
    119119 
    120120