Re: RFC: Dropping Windows XP support

2014-11-13 Thread Bulat Ziganshin
Hello Austin, Friday, November 7, 2014, 9:16:22 PM, you wrote: For one, Microsoft doesn't support XP anymore, so most people are moving off it anyway. 'Soon' even XP Embedded will be obsoleted. at the end of http://freearc.org/Statistics.aspx page you can find stats about OS used by

Re: GHC 7.8.3 thread hang

2014-11-13 Thread Gregory Collins
On Wed, Nov 12, 2014 at 10:01 PM, Michael Jones m...@proclivis.com wrote: Can you give some examples of what I should be looking for? Without seeing the relevant source code I don't see how to help you further. Re: blackholes, are you (or any code you're calling) using the par combinator? G

Re: RFC: Dropping Windows XP support

2014-11-13 Thread Bardur Arantsson
On 2014-11-13 15:25, Bulat Ziganshin wrote: Hello Austin, Friday, November 7, 2014, 9:16:22 PM, you wrote: For one, Microsoft doesn't support XP anymore, so most people are moving off it anyway. 'Soon' even XP Embedded will be obsoleted. at the end of

Re: Rules for class methods and Safe Haskell

2014-11-13 Thread Wolfgang Jeltsch
Am Freitag, den 15.08.2014, 23:10 +0300 schrieb Wolfgang Jeltsch: Hi, the module Control.Arrow declares a set of rules for the Arrow class. It is marked “Trustworthy”, probably to allow these rules to actually fire. Now these rules are only correct for class instances that actually

Under what conditions are finalizers not run?

2014-11-13 Thread Wolfgang Jeltsch
Hi, the documentation of System.Mem.Weak under http://hackage.haskell.org/package/base-4.7.0.1/docs/System-Mem-Weak.html says the following: It is not guaranteed that a finalizer will eventually run, and no attempt is made to run outstanding finalizers when the program exits. In which

Re: Rules for class methods and Safe Haskell

2014-11-13 Thread David Feuer
That's an interesting question. I'm not even close to an expert, but I *think* that parametricity prevents those particular rules from breaking Safe Haskell guarantees. The laws may not *hold* for a broken instance, but I don't *think* that lets you break type safety or IO encapsulation. On Nov

More flexible literate Haskell extensions (Trac #9789), summary on wiki

2014-11-13 Thread Merijn Verstraaten
As requested on my ticket I summarised the entire proposal on the wiki here: https://ghc.haskell.org/trac/ghc/wiki/FlexibleLiterateExtension I don't expect a lot of disagreement on discussion, aside from minor bike shedding on the flavour of the extension. I've started implementing this

Re: More flexible literate Haskell extensions (Trac #9789), summary on wiki

2014-11-13 Thread Simon Hengel
I don't expect a lot of disagreement on discussion, aside from minor bike shedding on the flavour of the extension. I've started implementing this already. I'm open to bikesheds on exact extension, as it shouldn't affect the implementation. Joining the party late, my main use case for