I think you're making this way harder than it really is.
What 99% of people need is that hackage packages builds with the latest
haskell platform, and/or with bleeding edge ghc, and with the latest
versions of its dependencies.
Thus for every dependency there is only one possible version - the
On Fri, 31 Aug 2012, Alexander Kjeldaas alexander.kjeld...@gmail.com wrote:
I think you're making this way harder than it really is.
What 99% of people need is that hackage packages builds with the latest
haskell platform, and/or with bleeding edge ghc, and with the latest
versions of its
Interesting data point. I think my initial thoughts can be summarized with
the suggestion that this thread would be better served by a little irony
and a new subject: Reuse Considered Harmful.
On Thu, Aug 30, 2012 at 1:26 AM, Bryan O'Sullivan b...@serpentine.comwrote:
Since the release of the
On 30 August 2012 15:26, Bryan O'Sullivan b...@serpentine.com wrote:
The reasons for these problems fall into three bins:
Prelude no longer exports catch, so a lot of import Prelude hiding (catch)
had to change.
It looks like this might be fixed before the release:
On 30/08/2012, at 5:26 PM, Bryan O'Sullivan wrote:
The reasons for these problems fall into three bins:
• Prelude no longer exports catch, so a lot of import Prelude hiding
(catch) had to change.
This could have been avoided if
import module hiding (importables)
were
On Thu, Aug 30, 2012 at 7:26 AM, Bryan O'Sullivan b...@serpentine.com wrote:
The FFI now requires constructors to be visible, so CInt has to be
imported as CInt(..).
I think there was already a warning about this one in GHC 7.4, so
there was more time to fix it. Not to say I don't feel your
This is very unfortunate, but this is crucially a tooling issue. I am
going to wave my hands, but..
Ignore the mapreduce in the following video, but look at the use of clang
to do automatic refactoring of C++. This is *incredibly* powerful in
dealing with updates to APIs.
Hi
I agree that automatic code migration can solve this issue in large
parts. The Python folks have done this to mitigate the transition from
version 2 to version 3 [1].
On Thu, Aug 30, 2012 at 03:03:05PM +0200, Alexander Kjeldaas wrote:
perl -ni -e 'print unless /import Prelude hiding
On 30 August 2012 15:34, Alexander Bernauer alex-hask...@copton.net wrote:
Hi
I agree that automatic code migration can solve this issue in large
parts. The Python folks have done this to mitigate the transition from
version 2 to version 3 [1].
On Thu, Aug 30, 2012 at 03:03:05PM +0200,
Note that this does not work if you want to support multiple versions
of GHC, and might not work in general, since
* The hiding of catch is needed for preludes that still have it, since
otherwise it will probably conflict with the one from
Control.Exception.
* Older versions do not have
On 8/30/12 10:26 AM, Erik Hesselink wrote:
Note that this does not work if you want to support multiple versions
of GHC, and might not work in general, since
* The hiding of catch is needed for preludes that still have it, since
otherwise it will probably conflict with the one from
A good way to specify such refactorings is as a Haskell module. For example:
module PreludePre_7_6 where
import Prelude hiding ( catch )
Or, an example of avoiding the Eq / Show / Num debacle:
module PreludePre_7_4 (module Prelude, Num) where
import Prelude hiding ( Num )
import qualified
Whoops, I messed up that first example:
module PreludePre_7_6 (module Prelude, catch) where
import Prelude
import qualified System.IO.Error as E
catch = E.catch
On Thu, Aug 30, 2012 at 12:16 PM, Michael Sloan mgsl...@gmail.com wrote:
A good way to specify such refactorings is as a Haskell
On Thu, Aug 30, 2012 at 7:24 PM, wren ng thornton w...@freegeek.org wrote:
On 8/30/12 10:26 AM, Erik Hesselink wrote:
* Packages might not work with the new bytestring version, since the
API has breaking changes (although they're supposed to be minor).
For the first two, you need to add some
On Thu, 30 Aug 2012, Alexander Kjeldaas alexander.kjeld...@gmail.com wrote:
This is very unfortunate, but this is crucially a tooling issue. I am
going to wave my hands, but..
Ignore the mapreduce in the following video, but look at the use of clang
to do automatic refactoring of C++. This
Since the release of the GHC 7.6 RC, I've been going through my packages
and fixing up build problems so that people who upgrade to 7.6 will have a
smooth ride.
Sad to say, my experience of 7.6 is that it has felt like a particularly
rough release for backwards incompatibility. I wanted to
16 matches
Mail list logo
