Hi,
On Tue, Jan 24, 2012 at 4:53 AM, Evan Laforge qdun...@gmail.com wrote:
[...]
So ghc --make provides two things: a dependency chaser and a way to
keep the compiler resident as it compiles new files. Since the
dependency chaser will never be as powerful as a real build system, it
occurs
From: Heka Treep zena.tr...@gmail.com
Subject: Re: Is it true that an exception is always terminates the
thread?
To: Edward Z. Yang ezy...@mit.edu
Cc: glasgow-haskell-users glasgow-haskell-users@haskell.org
Message-ID:
Hi,
On Tue, Jan 24, 2012 at 4:53 AM, Evan Laforge qdun...@gmail.com wrote:
So ghc --make provides two things: a dependency chaser and a way to
keep the compiler resident as it compiles new files. Since the
dependency chaser will never be as powerful as a real build system, it
occurs to me
One immediate problem I see with this is linking - 'ghc --make
Main.hs' is able to figure out what packages a program depends on,
while 'ghc Main.o ... -o Main' requires the user to specify them
manually with -package. So you'll either need to pass this information
back to the parent process,
Hi,
On Tue, Jan 24, 2012 at 7:04 PM, Evan Laforge qdun...@gmail.com wrote:
I'm also interested in a build server mode for ghc. I have written a
parallel wrapper for 'ghc --make' [1], but the speed gains are not as
impressive [2] as I hoped because of the duplicated work.
Was the duplicated
Hi Burak.
You seem to assume that old strategies use a different GC policy than
new strategies. My understanding is that this is not true. The WEAK
policy is used in general now. So old strategies shouldn't be used
with more recent GHCs, or you'll lose parallelism.
Cheers,
Andres
