On Wednesday, July 20, 2016, Ben Gamari wrote:
> Yuras Shumovich > writes:
>
> > Looks like reddit is a wrong place, so I'm replicating my comment here:
> >
> Thanks for your comments Yuras!
>
> >> * Do you feel the proposed process is an improvement over the
> >> status quo?
> >
> > Yes, defin
Ben Gamari writes:
> [ Unknown signature status ]
>
> Hello everyone,
>
> While picking up the pieces from a failed merge today I realized that we
> currently spend a fair bit of carbon footprint and CPU cycles making
> Travis test GHC yet the results of these tests aren't pushed anywhere.
>
> Wo
Hello everyone,
While picking up the pieces from a failed merge today I realized that we
currently spend a fair bit of carbon footprint and CPU cycles making
Travis test GHC yet the results of these tests aren't pushed anywhere.
Would anyone object to having Travis push notifications of changes
> 20 juli 2016 kl. 19:38 skrev amin...@gmail.com:
>
>
>
>> El 20 jul 2016, a las 12:45, Ben Gamari escribió:
>>
>> Iavor Diatchki writes:
>>
>>> Hello Ben,
>>>
>>> I posted this when you originally asked for feed-back, but perhaps it
>>> got buried among the rest of the e-mails.
>> Indeed
Iavor Diatchki writes:
> Hello Ben,
>
> I posted this when you originally asked for feed-back, but perhaps it
> got buried among the rest of the e-mails.
>
Indeed it seems that way. Sorry about that!
> I think the proposal sounds fairly reasonable, but it is hard to say how
> well it will work i
Yuras Shumovich writes:
> Looks like reddit is a wrong place, so I'm replicating my comment here:
>
Thanks for your comments Yuras!
>> * Do you feel the proposed process is an improvement over the
>> status quo?
>
> Yes, definitely. The existing process is too vague, so formalizing it
> is a w
Hello Ben,
I posted this when you originally asked for feed-back, but perhaps it
got buried among the rest of the e-mails.
I think the proposal sounds fairly reasonable, but it is hard to say how
well it will work in practice until we try it, and we should be ready to
change it if needs be.
Some
Is it my imagination or is git.haskell.org really slow at the moment?
SImion
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
Hopefully at a future date they will be a part of the AST itself, so this
will be clearer.
In reality, looking at Parser.y is not enough, as there are some workings
in RdrHsSyn.hs too, and the process of attachment in Parser.y is sometimes
quite complex.
Basically the best reference is indeed ghc
I think the most important thing is to be able to point to a designated
point where discussions must take place. This means if anything comes up
elsewhere it can be routed there to be "official".
Alan
On Wed, Jul 20, 2016 at 1:42 PM, Yuras Shumovich
wrote:
>
> Looks like reddit is a wrong place
On Wed, Jul 20, 2016 at 12:22 PM, Ben Gamari wrote:
> Matthew Pickering writes:
>
>> These comments are meant to indicate which annotations each AST
>> fragment has. However, they are rarely kept up to date and ultimately
>> not that useful. If someone wants to
>> know then it is easier to look a
Looks like reddit is a wrong place, so I'm replicating my comment here:
On Wed, 2016-07-20 at 11:36 +0200, Ben Gamari wrote:
> Hello everyone,
>
> As you hopefully know, a few weeks ago we proposed a new process [1]
> for
> collecting, discussing, and deciding upon changes to GHC and its
> Haske
Matthew Pickering writes:
> These comments are meant to indicate which annotations each AST
> fragment has. However, they are rarely kept up to date and ultimately
> not that useful. If someone wants to
> know then it is easier to look at the `Annotate` module in
> `ghc-exactprint`where this info
On 20 July 2016 at 11:36, Ben Gamari wrote:
> * Do you feel the proposed process is an improvement over the status
> quo?
>
> * Why? (this needn't be long, just a sentence hitting the major points)
For a considerable part of the community it seems to be an
improvement, so yes.
> * What
>
> * What would you like to see changed in the proposed process, if
> anything?
>
*Simon Peyton Jones as Benevolent Dictator For Life (BDFL)*
If the BDFL had made a simple YES/NO decision on ShortImports [1] and
ArgumentDo [2], we wouldn't be here talking about process proposals,
Anthony w
These comments are meant to indicate which annotations each AST
fragment has. However, they are rarely kept up to date and ultimately
not that useful. If someone wants to
know then it is easier to look at the `Annotate` module in
`ghc-exactprint`where this information also exists programatically.
Hello everyone,
As you hopefully know, a few weeks ago we proposed a new process [1] for
collecting, discussing, and deciding upon changes to GHC and its Haskell
superset. While we have been happy to see a small contingent of
contributors join the discussion, the number is significantly smaller
t
I see some weird comments like
-- - 'ApiAnnotation.AnnKeywordId' : 'ApiAnnotation.AnnOpen',
-- 'ApiAnnotation.AnnVbar','ApiAnnotation.AnnComma',
-- 'ApiAnnotation.AnnClose'
-- For details on above see note [Api annotations] in ApiAnnotation
in some file
18 matches
Mail list logo
