GHC.Event.Unique vs Data.Unique

Is there a reason GHC.Event.Unique exists, since we also have Data.Unique? Or is this just a historical artifact? It looks like they used to have the same implementation, but have now diverged, with Data.Unique being the more recent one. GHC.Event.Unique still uses STM internally, and is as far

Re: [commit: ghc] master: Bump haddock.base max_bytes_used (8df7fea)

Hi, Am Freitag, den 01.08.2014, 23:27 +0200 schrieb Joachim Breitner: Am Freitag, den 01.08.2014, 20:28 + schrieb Simon Peyton Jones: Urk. It's quite surprising that this particular change would increase allocation significantly. I wonder whether it just pushed it over the

Re: Interrupt interruptible foreign calls on HS exit

Thanks Edward! Another question... deleteThread() calls throwToSingleThreaded(). I can update this so that it also calls throwToSingleThreaded() in the case of BlockedOnCCall_Interruptible (currently it explicitly excludes this case), but this doesn't solve the problem, because

Re: GHC.Event.Unique vs Data.Unique

Despite having the same name, these two are quite different from what I remember. The GHC.Event one (which me/Bryan added) is just a wrapped Int, while the Data one is really more of a mutable state thing. On Sat, Aug 2, 2014 at 8:40 AM, Michael Schröder mc.schroe...@gmail.com wrote: Is there a

Re: Interrupt interruptible foreign calls on HS exit

I tried to go ahead and call throwTo() instead of throwToSingleThreaded() for threads BlockedOnCCall_Interruptible state during the shutdown sequence. Unfortunately something goes wrong with this change. I haven't tracked it down yet, but it looks like the following happens... hs_exit()