On Thu, May 03, 2007 at 04:59:58PM -0700, John Meacham wrote:
I believe it is because a stack cannot be garbage collected, and must be
traversed as roots for every garbage collection. I don't think there are
any issues with a huge stack per se, but it does not play nice with
garbage collection
Sending to the right list this time, with some additions.
Just to show what kind of problems we are currently facing. The
following type checks in our EHC compiler and in Hugs, but not in the
GHC:
module Test where
data T s = forall x. T (s - (x - s) - (x, s, Int))
run :: (forall
On Wed, Feb 14, 2007 at 10:04:32AM +, Simon Marlow wrote:
Perhaps I'm missing something, but doesn't GHC already detect the kind of
deadlock you're talking about here? When a thread is blocked and cannot be
woken up, it is sent the BlockedOnDeadMVar exception. It's more precise
than
