| Clearly, in this instance GHC is not transforming either of these
| definitions into the other. But are there other compile time
transformations
| performed by GHC that might result in more (excessive) sharing, in
| particular the creation of new common sub-expressions such as pxs? If
not,
| is t
It's all very delicate. I believe, though I am not certain, that in the
absence of functional dependencies, removing at least one type
constructor might be an example of a rule that is sufficient to ensure
termination. There are lots of such rules. Alas none known to me
capture all cases.
Functi
Simon Peyton-Jones wrote:
It's all very delicate. I believe, though I am not certain, that in the
absence of functional dependencies, removing at least one type
constructor might be an example of a rule that is sufficient to ensure
termination. There are lots of such rules. Alas none known to m
It seems that you can do this as long as you provide your own version of
forkIO, but not if you want to use the built-in forkIO.
One could argue that getting the parent ThreadId is something that
should be supported natively by forkIO, and I might be inlined to agree.
Unfortunately there are some
What about adding support for hooks in forkIO? These could be useful
for other things as well. Pthreads could be said to have this
functionality:
-- Function: int pthread_atfork (void (*PREPARE)(void), void
(*PARENT)(void), void (*CHILD)(void))
`pthread_atfork' registers handler fu
Haskell Weekly News: October 18, 2005
Greetings, and thanks for reading the 12th issue of HWN, a weekly
newsletter for the Haskell community. Each Tuesday, new editions will be
posted (as text) to [1]the Haskell mailing list and (as HTML) to [2]The
Haskell Sequence
On Tue, Oct 18, 2005 at 08:31:19AM +0100, Simon Peyton-Jones wrote:
> GHC tries not to create space leaks, but does not guarantee not to. In
> particular, the full laziness transformation is so beneficial most of
> the time that, even though it can create a space leak GHC still does it
> (unless y
John Meacham wrote:
On Tue, Oct 18, 2005 at 08:31:19AM +0100, Simon Peyton-Jones wrote:
GHC tries not to create space leaks, but does not guarantee not to. In
particular, the full laziness transformation is so beneficial most of
the time that, even though it can create a space leak GHC still do
On Wed, Oct 19, 2005 at 12:01:07AM +0200, Daan Leijen wrote:
> John Meacham wrote:
> >On Tue, Oct 18, 2005 at 08:31:19AM +0100, Simon Peyton-Jones wrote:
> >>GHC tries not to create space leaks, but does not guarantee not to. In
> >>particular, the full laziness transformation is so beneficial mos
On Tue, Oct 18, 2005 at 07:12:13PM +0100, Frederik Eaton wrote:
> (Pthreads also has support for "thread-specific data":
>
> -- Function: int pthread_setspecific (pthread_key_t KEY, const void
> *POINTER)
> `pthread_setspecific' changes the value associated with KEY in the
10 matches
Mail list logo
