[commit: ghc] master: Fire "map/coerce" only in phase 1 (f764aac)

[git at git.haskell.org]

Repository : ssh://git@git.haskell.org/ghc

On branch  : master
Link       : http://ghc.haskell.org/trac/ghc/changeset/f764aac57fdf3eefef6bada0a62aae5e95cec847/ghc

>---------------------------------------------------------------

commit f764aac57fdf3eefef6bada0a62aae5e95cec847
Author: Joachim Breitner <mail at joachim-breitner.de>
Date:   Tue Jun 10 16:13:17 2014 +0200

    Fire "map/coerce" only in phase 1
    
    I just noticed a lot of warnings
    
    	Rules.findBest: rule overlap (Rule 1 wins)
    	    Rule 1: "map"
    	    Rule 2: "map/coerce"
    
    which can easily be avoided by acitivating map/coerce only from phase 1
    on.


>---------------------------------------------------------------

f764aac57fdf3eefef6bada0a62aae5e95cec847
 libraries/base/GHC/Base.lhs | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/libraries/base/GHC/Base.lhs b/libraries/base/GHC/Base.lhs
index 1c8e144..f4f3454 100644
--- a/libraries/base/GHC/Base.lhs
+++ b/libraries/base/GHC/Base.lhs
@@ -406,7 +406,7 @@ mapFB c f = \x ys -> c (f x) ys
 --
 --   http://research.microsoft.com/en-us/um/people/simonpj/papers/ext-f/coercible.pdf
 
-{-# RULES "map/coerce" map coerce = coerce #-}
+{-# RULES [1] "map/coerce" map coerce = coerce #-}
 
 \end{code}