summaryrefslogtreecommitdiff
path: root/libraries
diff options
context:
space:
mode:
authorJoachim Breitner <mail@joachim-breitner.de>2014-06-10 16:13:17 +0200
committerJoachim Breitner <mail@joachim-breitner.de>2014-06-10 16:13:17 +0200
commitf764aac57fdf3eefef6bada0a62aae5e95cec847 (patch)
treed9f7298314a6c4097c6db4cab71a2772c5189df2 /libraries
parentfaddad7ec6e5738987d5571ad23054a5aa39c193 (diff)
downloadhaskell-f764aac57fdf3eefef6bada0a62aae5e95cec847.tar.gz
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.
Diffstat (limited to 'libraries')
-rw-r--r--libraries/base/GHC/Base.lhs2
1 files changed, 1 insertions, 1 deletions
diff --git a/libraries/base/GHC/Base.lhs b/libraries/base/GHC/Base.lhs
index 1c8e144b7f..f4f3454d6d 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}