GHC 7.8.3 release

2014-05-27 Thread Austin Seipp
Hello all, After a long week, I've finally gotten a little time to reply to emails, and I mainly have one question I'd like to ask. First, please direct your attention to this:

Re: GHC 7.8.3 release

2014-05-27 Thread 山本和彦
Hi Austin, I ask this because my time to dedicate to GHC is a bit thin right now, so you must help me decide what's important! So please let me know - just a general vote in favor of doing it within some X timeframe (even 'real soon' or 'a week would be great') would be nice. Would you give

Re: GHC 7.8.3 release

2014-05-27 Thread Michael Snoyman
I'm building the GHC-7.8 branch now, and will then kick off a Stackage build. That should give a good indication if there are regressions. On Tue, May 27, 2014 at 11:06 AM, Austin Seipp aus...@well-typed.comwrote: Hello all, After a long week, I've finally gotten a little time to reply to

Re: GHC 7.8.3 release

2014-05-27 Thread Johan Tibell
I would say sooner. Here are still unmerged things that I think we could merge before (i.e. easy to merge): https://ghc.haskell.org/trac/ghc/ticket/9001 https://ghc.haskell.org/trac/ghc/ticket/9078 https://ghc.haskell.org/trac/ghc/ticket/8475 https://ghc.haskell.org/trac/ghc/ticket/8783

Re: GHC 7.8.3 release

2014-05-27 Thread Manuel M T Chakravarty
I believe #9078 affects all EDSLs that use Andy Gill’s stable name method to implement observable sharing. It certainly crashes Accelerate. I would very much appreciate if 7.8.3 would be released in time to make it into the upcoming Haskell Platform. (If the platform would ship with 7.8.2.,

Re: GHC 7.8.3 release

2014-05-27 Thread Niklas Larsson
Hi! It would be great if the patch I added on #9080 was put into 7.8.3 (well, I guess someone has to commit it to master first). Niklas 2014-05-27 10:06 GMT+02:00 Austin Seipp aus...@well-typed.com: Hello all, After a long week, I've finally gotten a little time to reply to emails, and I

Re: GHC 7.8.3 release

2014-05-27 Thread Austin Seipp
Hi Niklas, Yes, that patch looks great, thank you. The only reason it wasn't included in the list earlier was that the status was set to 'new', not to 'patch!' I'm afraid this is perhaps the most critical aspect necessary for me to recognize such tickets. I have marked it as patch, and it can go