- Apr 28, 2010
-
- Nov 29, 2009
-
-
Ian Lynagh authored
-
- Sep 20, 2009
-
-
Ian Lynagh authored
-
- Aug 27, 2009
-
-
Simon Marlow authored
-
- Aug 11, 2009
-
-
Ian Lynagh authored
-
- Aug 02, 2009
-
-
Ian Lynagh authored
It is now in its own diffarray package
-
- Jul 19, 2009
-
-
Ian Lynagh authored
As well as checking that offset we are reading is actually inside the array, we now also check that it is "in range" as defined by the Ix instance. This fixes confusing behaviour (#2120) and improves some error messages (#2669).
-
- Jul 10, 2009
-
-
Ian Lynagh authored
-
- Feb 02, 2009
-
- Apr 24, 2009
-
-
Ian Lynagh authored
-
- Jan 22, 2009
-
-
Ian Lynagh authored
-
- Jan 21, 2009
-
-
Ian Lynagh authored
-
- Jan 04, 2009
-
-
Ian Lynagh authored
-
- Dec 12, 2008
-
-
Ian Lynagh authored
-
- Nov 13, 2008
-
-
Duncan Coutts authored
-
- Oct 02, 2008
-
-
dreixel authored
-
- Sep 20, 2008
-
-
Ian Lynagh authored
-
- Sep 03, 2008
-
- Aug 31, 2008
-
-
Ross Paterson authored
-
- Aug 28, 2008
-
-
Malcolm.Wallace@cs.york.ac.uk authored
-
- Aug 25, 2008
-
-
Ian Lynagh authored
-
- Aug 24, 2008
-
-
Ross Paterson authored
-
- Aug 23, 2008
-
-
Ross Paterson authored
-
Ross Paterson authored
-
- Aug 24, 2008
-
-
Ian Lynagh authored
-
- Aug 23, 2008
-
-
Ian Lynagh authored
-
- Aug 16, 2008
-
-
Ian Lynagh authored
-
- Aug 17, 2008
-
-
Ross Paterson authored
These instances aren't orphans; they'll be available if Foldable or Traversable are. They shouldn't be here because then they'd leak the instances in Control.Monad.Instances into the Haskell 98 module Array.
-
- Aug 16, 2008
-
-
Ian Lynagh authored
-
Ross Paterson authored
-
- Aug 04, 2008
-
-
simonpj@microsoft.com authored
Now that orphan warnings obey -Werror, we must suppress them when they occur. I'd prefer that these three modules didn't have orphans; Ian is going to look into this.
-
- Aug 03, 2008
-
-
Ian Lynagh authored
These are no longer needed, now that Prelude is in a different package
-
- Jul 05, 2008
-
-
Ross Paterson authored
-
- Jun 30, 2008
-
-
Ian Lynagh authored
-
- Jun 19, 2008
-
-
Ian Lynagh authored
-
- Jun 16, 2008
-
-
Ian Lynagh authored
-
- Mar 25, 2008
-
-
Duncan Coutts authored
Specify the build-type and min cabal-version. Don't have Data.Array in both exposed-modules on both sides of a conditional, just make it unconditional. Stop using -fglasgow-exts and specify all the extensions explicitly. Some extensions are conditional on non-nhc98 and some are ghc-specific.
-
Duncan Coutts authored
-
Duncan Coutts authored
The real reason to not import Control.Applicative is that it exports the non-H98 instance Functor ((->) a) and it is important for Data.Array to not re-export that because the H98 Array module re-exports bits of Data.Array and it is vital that we do not export non-H98 instances from a module specified in H98.
-
- Mar 02, 2008
-
-
Matti Niemenmaa authored
-