summaryrefslogtreecommitdiff
path: root/compiler/utils/MonadUtils.hs
diff options
context:
space:
mode:
authorHerbert Valerio Riedel <hvr@gnu.org>2015-03-07 11:10:34 +0100
committerHerbert Valerio Riedel <hvr@gnu.org>2015-03-07 11:10:53 +0100
commiteb3661f2b9f8472f3714774126ebe1183484dd85 (patch)
tree2153640f3a87a099ea1bcd399f327fb8600c7ebc /compiler/utils/MonadUtils.hs
parent1965202febe27949a027dea90c0f0040fd9236e7 (diff)
downloadhaskell-eb3661f2b9f8472f3714774126ebe1183484dd85.tar.gz
Re-export `<$>` from Prelude (#10113)
Whether to re-export the `<$>` non-method operator from `Prelude` wasn't explicitly covered in the original AMP proposal[1], but it turns out that not doing so forces most code that makes use of applicatives to import `Data.Functor` or `Control.Applicative` just to get that operator into scope. To this end, it was proposed to add `<$>` to Prelude as well[2]. The down-side is that this increases the amount of redundant-import warnings triggered, as well as the relatively minor issue of stealing the `<$>` operator from the default namespace for good (although at this point `<$>` is supposed to be ubiquitous anyway due to `Applicative` being implicitly required into the next Haskell Report) [1]: https://wiki.haskell.org/Functor-Applicative-Monad_Proposal [2]: http://thread.gmane.org/gmane.comp.lang.haskell.libraries/24161 Reviewed By: austin, ekmett Differential Revision: https://phabricator.haskell.org/D680
Diffstat (limited to 'compiler/utils/MonadUtils.hs')
-rw-r--r--compiler/utils/MonadUtils.hs1
1 files changed, 1 insertions, 0 deletions
diff --git a/compiler/utils/MonadUtils.hs b/compiler/utils/MonadUtils.hs
index 0850ff43c4..e20178c4f8 100644
--- a/compiler/utils/MonadUtils.hs
+++ b/compiler/utils/MonadUtils.hs
@@ -34,6 +34,7 @@ import Control.Applicative
import Control.Monad
import Control.Monad.Fix
import Control.Monad.IO.Class
+import Prelude -- avoid redundant import warning due to AMP
-------------------------------------------------------------------------------
-- Lift combinators