Brian Hulley wrote:
I'm wondering if the monomorphism restriction is now just an anachronism
from Haskell 98 or if it is still needed for efficiency ie should I just
now use -fno-monomorphism-restriction when compiling all my code to
consign it to the dustbin of history? :-)
A related
On Fri, Jun 02, 2006 at 05:35:20PM +0200, Christian Maeder wrote:
Hi,
[..]
you need to build the whole tree (using gmake) with a file mk/build.mk
that just contains the lines:
[..]
I will try it.
I guess, because 6.4.3 includes some fixes, it make sense to do the
packaging for that version
On Fri, Jun 02, 2006 at 03:59:01PM +0100, Duncan Coutts wrote:
Hi,
On Fri, 2006-06-02 at 15:10 +0200, Georg Sauthoff wrote:
at http://hackage.haskell.org/trac/ghc/wiki/Platforms I read, that the
Sparc NCG 'is bitrotted' - does that mean, that it is unmaintained, but
used by default at
On Mon, 2006-06-12 at 18:38 +0200, Georg Sauthoff wrote:
On Fri, Jun 02, 2006 at 03:59:01PM +0100, Duncan Coutts wrote:
On Fri, 2006-06-02 at 15:10 +0200, Georg Sauthoff wrote:
at http://hackage.haskell.org/trac/ghc/wiki/Platforms I read, that the
Sparc NCG 'is bitrotted' - does that
Simon Marlow wrote:
Brian Hulley wrote:
I'm wondering if the monomorphism restriction is now just an
anachronism from Haskell 98 or if it is still needed for efficiency
ie should I just now use -fno-monomorphism-restriction when
compiling all my code to consign it to the dustbin of history?
