Especially in the case of base, not sure how upper bounds help at all:
If incompatible, you break with or without upper bounds. Actually getting
errors related to Num instances is more informative IMO.
If compatible, you just get false negatives and errors.
In either case cabal can't install an
Hi,
I would like to suggest a change to Haskell prime's handling of
imports.
First, let me define a few terms:
Qualified import:
import qualified Data.Map [as Map]
Closed-unqualified import:
import Data.Map(Map, lookup)
Open-unqualified import:
import Data.Map
I believe that the last type, op
Very nice series of refactorings!
I'd like to add that it might be a better argument order to replace:
JSON a => MyData -> String -> a -> MyData
with:
JSON a => String -> a -> MyData -> MyData
Just so you can get a (MyData -> MyData) transformer, which is often
useful.
Eyal
On Jan 16, 1:52 a
If this is valid:
import qualified Control.Exception as Exc
genericFromException :: Typeable a => Exc.SomeException -> Maybe a
genericFromException (Exc.SomeException e) = cast e
instance Exc.Exception SomeType where fromException =
genericFromException
then why not have an auto-
