Personally I think commit messages should be formatting-free.
* I type them into an emacs buffer, with no way to preview any formatting.
* When viewing with git log or other such tools, the formatting just
gets in the way
Is it easy to change?
Simon
| -Original Message-
| From: ghc-d
Unless I missed an RC announcement, I'm pretty sure we're running a little
behind the schedule from that email.
Deciders, has the Nov 25 target slid back? Any new estimates, if so?
Thanks much.
On Nov 14, 2013 9:40 PM, "Andreas Voellmy"
wrote:
>
>
>
> On Thu, Nov 14, 2013 at 10:38 PM, Andreas V
On Thu, Nov 14, 2013 at 10:38 PM, Andreas Voellmy wrote:
> I added a note about the parallel IO manager status to
> https://ghc.haskell.org/trac/ghc/wiki/Status/GHC-7.8. There are two
> issues I'd still like to resolve. Is there a target date for the release?
>
Oh, I just noticed
http://permali
I added a note about the parallel IO manager status to
https://ghc.haskell.org/trac/ghc/wiki/Status/GHC-7.8. There are two issues
I'd still like to resolve. Is there a target date for the release?
-Andi
On Fri, Nov 8, 2013 at 12:02 AM, Andreas Voellmy
wrote:
> Yes, the parallel IO manager is n
Hi Bryan,
I apologize for not bringing this issue up in a more timely fashion.
I'm curious why the Bundle support that Roman added to the vector
library was removed. I understand that the change in representation made
it difficult for, e.g., dph to use the new vector library, but this
change in r
On Thu, Nov 14, 2013 at 11:25 AM, Geoffrey Mainland wrote:
> Perhaps the roll-back in functionality was just done to get 7.8 out the
> door?
>
That's correct. Also, the vector repo was never properly tagged, so it was
impossible to untangle the work in progress on bundles from anything stable.
__
Good idea! I made the change in commit
19b8809c477f4d296cbd6c1736e9a288fdcd6220.
On Wed, Nov 13, 2013 at 6:57 PM, Simon Peyton-Jones
wrote:
> That is indeed revolting.
>
> Why not make
> sfMatchFam :: [Type] -> Maybe (CoAxiomRule, [Type], Type)
> thus getting rid of the TcCoercion, and ba
On 2013-11-14 at 13:07:00 +0100, Simon Marlow wrote:
[...]
> Obviously this is all just MHO, if everyone else wants markup in
> commit messages then I won't complain.
btw, I'm keeping my eyes open to see how easy it'd be to support
specific renderer for commit messages, with a simple/reasonable
On 14/11/13 10:11, Herbert Valerio Riedel wrote:
On 2013-11-13 at 11:36:13 +0100, Simon Marlow wrote:
On 12/11/13 15:53, Joachim Breitner wrote:
Am Dienstag, den 12.11.2013, 15:24 + schrieb Simon Peyton-Jones:
When Trac formats commit messages it is doing a terrible job. See for
example:
After fixing the warning in the C-code of the primitive package, validate
(including dph tests) seems to be working for me:
OVERALL SUMMARY for test run started at Thu Nov 14 11:03:26 2013 CET
0:46:34 spent to go through
3818 total tests, which gave rise to
14930 test cases, of which
1
On 2013-11-13 at 11:36:13 +0100, Simon Marlow wrote:
> On 12/11/13 15:53, Joachim Breitner wrote:
>
>> Am Dienstag, den 12.11.2013, 15:24 + schrieb Simon Peyton-Jones:
>>> When Trac formats commit messages it is doing a terrible job. See for
>>> example: https://ghc.haskell.org/trac/ghc/ticket
Looking at the "offending" c-code of the primitive library, with my limited C
knowledge and understanding of this strict-aliasing, I think the gcc warning on
Lion is correct: the strict-aliasing rule is violated.
However, after asking my colleague, we don't think the gcc optimizer will break
th
This does raise a point I hope we'll address more aggressively after the 7.8
release, namely trying to keep ghc less broken by default! GHC being really
really really broken between releases is probably the single HUGEST barrier to
more people getting involved in helping GHC dev. And I think tha
13 matches
Mail list logo
