I’ve been made aware that the “NoFallibleDo” proposal has been re-submitted to the Committee. My current recommendation is “reject”, as outlined in the following comment https://github.com/ghc-proposals/ghc-proposals/pull/319#issuecomment-885580010 (TL;DR, you’d often like to enable this for a particular “do” block, not for an entire file).Regards,Alejandro
El 28 jul 2020 11:33:02, Alejandro Serrano Mena <trupill@gmail.com> escribió:Done. Once again, sorry for the confusion.AlejandroEl mar., 28 jul. 2020 a las 11:30, Simon Peyton Jones (<simonpj@microsoft.com>) escribió:OK, so to summarise
- We are waiting for the author
- You are encouraging us to comment anyway
Correct? Does the author know this? Why encourage only us? Maybe post on Github to clarify the status, and encourage everyone to contribute.
S
From: Alejandro Serrano Mena <trupill@gmail.com>
Sent: 28 July 2020 10:25
To: Simon Peyton Jones <simonpj@microsoft.com>
Cc: ghc-steering-committee@haskell.org
Subject: Re: [ghc-steering-committee] Please review #319: NoFallibleDo proposal, Shepherd: Eric Seidel
I mean the last status, push back to the author for revision.
Alejandro
El mar., 28 jul. 2020 a las 11:24, Simon Peyton Jones (<simonpj@microsoft.com>) escribió:
So I’m still confused. “We went back to GIthub”… does that mean that we invited the author to revise and resubmit? I don’t know what else “back to github” means.
If it’s in committee-decision status, then our process says should either accept, reject, or push back to the author for revision, in a timely way (guided by the shepherd)
Simon
From: Alejandro Serrano Mena <trupill@gmail.com>
Sent: 28 July 2020 10:22
To: Simon Peyton Jones <simonpj@microsoft.com>
Cc: ghc-steering-committee@haskell.org
Subject: Re: [ghc-steering-committee] Please review #319: NoFallibleDo proposal, Shepherd: Eric Seidel
Eric was initially in charge, but I took over his duties. He thought that a bit more discussion was needed, something I agree with, so we went back to GitHub.
Sorry about the stale status, I feel that my back-and-forth was not very clear.
Alejandro
El mar., 28 jul. 2020 a las 11:17, Simon Peyton Jones (<simonpj@microsoft.com>) escribió:
Alejandro, this one hasn’t been on my radar.
Are you the shepherd? Have you made a recommendation? Is the proposal in its final form -- ie having absorbed all discussion etc?
Simon
From: ghc-steering-committee <ghc-steering-committee-bounces@haskell.org> On Behalf Of Alejandro Serrano Mena
Sent: 28 July 2020 09:22
To: Joachim Breitner <mail@joachim-breitner.de>
Cc: ghc-steering-committee <ghc-steering-committee@haskell.org>
Subject: Re: [ghc-steering-committee] Please review #319: NoFallibleDo proposal, Shepherd: Eric Seidel
Dear Committee,
I would like to kindly ask for your input in the NoFallibleDo proposal -> https://github.com/ghc-proposals/ghc-proposals/pull/319
This was submitted, then there was some discussion, but the conversation has stalled.
Regards,
Alejandro
El jue., 14 may. 2020 a las 17:30, Alejandro Serrano Mena (<trupill@gmail.com>) escribió:
@Eric congratulations! enjoy! :)
@Joachim I can take care of this, I think the direction Eric was pushing this is a good one.
El jue., 14 may. 2020 a las 12:16, Joachim Breitner (<mail@joachim-breitner.de>) escribió:
Hi,
Am Mittwoch, den 13.05.2020, 15:19 -0500 schrieb Eric Seidel:
> My wife and I just checked into the hospital to have our second child
Congrats, and all the best!
> , so I’m going to be short on time for committee duties for a few
> weeks. I think it would be best to reassign this proposal so we don’t
> keep the authors waiting.
Any volunteers?
Cheers,
Joachim
--
Joachim Breitner
mail@joachim-breitner.de
http://www.joachim-breitner.de/
_______________________________________________
ghc-steering-committee mailing list
ghc-steering-committee@haskell.org
https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee