RE: expanding type synonyms in error messages

2015-06-19 Thread Simon Peyton Jones
On this thread, a representative collection of *reproducible examples* with the actual error message and the desired one, would be tremendously helpful. Lacking that, it’s hard to know where to begin. (Creating the examples takes a bit of work, I know.) Start a wiki page! Stuff in email

Re: expanding type synonyms in error messages

2015-06-19 Thread Richard Eisenberg
Don't forget to make a Feature Request on Trac (https://ghc.haskell.org/trac/ghc/newticket) with a link to the wiki page. Trac is really the only way things like this don't get lost. Thanks! Richard On Jun 19, 2015, at 9:07 AM, Ömer Sinan Ağacan omeraga...@gmail.com wrote: Great, thanks

Re: expanding type synonyms in error messages

2015-06-19 Thread Kostiantyn Rybnikov
Great, thanks for doing this! I'm afraid even if you succeed with patch we would still need more real-world examples that show the need for this feature, and I think this is separate from GHC tests, as they don't need to be realistic, but of course please continue and hopefully more examples will

Re: expanding type synonyms in error messages

2015-06-19 Thread Ömer Sinan Ağacan
Done: https://ghc.haskell.org/trac/ghc/ticket/10547 2015-06-19 9:12 GMT-04:00 Richard Eisenberg e...@cis.upenn.edu: Don't forget to make a Feature Request on Trac (https://ghc.haskell.org/trac/ghc/newticket) with a link to the wiki page. Trac is really the only way things like this don't get

Re: expanding type synonyms in error messages

2015-06-19 Thread Ömer Sinan Ağacan
Great, thanks Kostiantyn! I'm looking for simple examples that we can add to GHC testsuite, if I find something I'll update the wiki page also. I made some progress on the patch, I think I can hopefully submit something this weekend for reviews. 2015-06-19 5:16 GMT-04:00 Kostiantyn Rybnikov

RE: [Diffusion] [Build Failed] rGHCc45f8ceb0de0: Elaborate test for Trac #10403

2015-06-19 Thread Simon Peyton Jones
I think 4945 is failing again -- although not on my machine. Can someone mark it expect_broken again? I'm on a train S | -Original Message- | From: nore...@phabricator.haskell.org | [mailto:nore...@phabricator.haskell.org] | Sent: 19 June 2015 00:09 | To: Simon Peyton Jones | Subject:

Re: expanding type synonyms in error messages

2015-06-19 Thread Kostiantyn Rybnikov
Created some initial wiki-page with just one example, will keep it in mind to add more as seen. https://wiki.haskell.org/Expanding_type_synonyms_in_error_messages_proposal On Fri, Jun 19, 2015 at 10:42 AM, Simon Peyton Jones simo...@microsoft.com wrote: On this thread, a representative

Re: [Diffusion] [Build Failed] rGHCc45f8ceb0de0: Elaborate test for Trac #10403

2015-06-19 Thread Austin Seipp
Strange stuff. I just pushed this, so the builds should start going green again soon. On Fri, Jun 19, 2015 at 2:39 AM, Simon Peyton Jones simo...@microsoft.com wrote: I think 4945 is failing again -- although not on my machine. Can someone mark it expect_broken again? I'm on a train S |

Re: Native -XCPP Conclusion

2015-06-19 Thread Simon Marlow
I have no problem with plan 4. However, I'll point out that implementing CPP is not *that* hard... :) Cheers, Simon On 18/06/2015 09:32, Herbert Valerio Riedel wrote: Hello *, Following up on the Native -XCPP Proposal discussion, it appears that cpphs' current LGPL+SLE licensing doesn't