<div dir="ltr"><div class="gmail_default" style="font-family:tahoma,sans-serif">Shepherds: can I urge you to make progress on your proposals? It's bad when things like in our inbox for months. We should say yes/no/please-revise in a timely manner.</div><div class="gmail_default" style="font-family:tahoma,sans-serif"><br></div><div class="gmail_default" style="font-family:tahoma,sans-serif">If you can't do that, please say, and we'll figure something out.</div><div class="gmail_default" style="font-family:tahoma,sans-serif"><br></div><div class="gmail_default" style="font-family:tahoma,sans-serif">Thank you! <br></div><div class="gmail_default" style="font-family:tahoma,sans-serif"><br></div><div class="gmail_default" style="font-family:tahoma,sans-serif">Simon<br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, 19 Jan 2023 at 16:11, Joachim Breitner <<a href="mailto:mail@joachim-breitner.de">mail@joachim-breitner.de</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Dear Committee,<br>
<br>
it seems we need a reminder what’s on our respective plates, so prompted by<br>
Simon let’s do another status update. I strongly assume you are always reading<br>
these (rare!) emails, especially the second half that lists all our collective<br>
or individual TODO items.<br>
<br>
So what has happened since the last one?<br>
<br>
* The discussion whether we should have GHC2023 did not take off really,<br>
and forked into a somewhat useful, but unfinished fundamental discussion about<br>
the role of extensions, over at<br>
<a href="https://docs.google.com/document/d/1_-hPh8BRhKNlzM0dC1IRSmjCqPym9mXx9NjC7jUlpRQ/edit" rel="noreferrer" target="_blank">https://docs.google.com/document/d/1_-hPh8BRhKNlzM0dC1IRSmjCqPym9mXx9NjC7jUlpRQ/edit</a><br>
<br>
I’ll kick off a vote about GHC2023 in a few days (and by popular request I’ll<br>
simplify it to the simple question of whether we should have it at all; I get<br>
the feeling that my preference for frequent-over-big-changes is not shared and<br>
no need to vote on individual extensions if it won’t come that too)<br>
<br>
* we were asked to review these proposals:<br>
<br>
#523: let in types and patterns, Shepherd: Adam<br>
#555: Higher Order Patterns in Rewrite Rules, Shepherd Joachim <br>
<br>
* we have a recommendation from the shepherd about:<br>
<br>
#512: NoFieldSelectors as datatype annotations, Rec: reject<br>
#270: Support pun-free code. Recommendation: accept<br>
#546: Make Symbol a newtype over String, Rec: accept<br>
#555: Higher Order Patterns in Rewrite Rules, Rec: accept<br>
<br>
* we have sent the following proposals back to revision<br>
<br>
#330: Decorate exceptions with backtrace information<br>
<br>
* we decided about the following proposals<br>
<br>
#541: Warning pragma with categories (accept)<br>
#522: Or patterns (accept)<br>
<br>
* the authors retracted their proposal<br>
<br>
#523: let in types and patterns, Shepherd: Adam<br>
<br>
We currently have to act on the following 10 proposals, two down<br>
from last time, but still high:<br>
<br>
## Waiting for committee decision<br>
<br>
#270: Support pun-free code, Shepherd: Chris<br>
2022-01-01: Assigned to Chris<br>
2022-08-24: Chris suggests acceptance<br>
2022-12-04: Chris suggests acceptance again<br>
2022-12-15: Last message<br>
I’ve paged out where we are on this one.<br>
Something with ExplicitNamespaces?<br>
<br>
#532: Clean up implicit binding, Shepherd: Arnaud <br>
2022-08-23: Assigned to Arnaud<br>
Sent back for revision<br>
2022-11-27: Resubmitted<br>
2022-12-14: Arnaud recommends acceptance<br>
Arnaud just picked up the conversation again.<br>
Please make it converge.<br>
<br>
#515: Relaxing HasField constraints<br>
2022-08-01: Assigned to Tom<br>
2022-08-10: Tom suggests acceptance<br>
Tom, please drive this forward!<br>
<br>
#512: NoFieldSelectors as datatype annotation, Shepherd: Vlad<br>
2022-09-03: Assignd to Baldur<br>
2022-10-02: Reassignd to Vlad<br>
2022-11-30: Vlad recommends rejection<br>
Turned into a discussion of Modifiers.<br>
Where are we on this one?<br>
<br>
#555: Higher Order Patterns in Rewrite Rules, Shepherd Joachim <br>
2023-01-10: Acceptance recommended<br>
Mostly silence. I expect to merge this in a week or so.<br>
<br>
#546: Make Symbol a newtype over String, Shepherd: Chris<br>
2022-11-18: Assigned to Chris<br>
2022-09-12: Authors gave up<br>
2023-01-19: Chris revived (as #562) and rec’s acceptance<br>
<br>
<br>
## Waiting for shepherd recommendation<br>
<br>
#526: Applicative Comprehensions, Shepherd: Simon M<br>
2022-10-08: Assigned to Simon M<br>
<br>
#529: Template Haskell quotes as patterns, Shepherd: Adam<br>
2022-11-16: Assigned to Adam<br>
(should this be “needs revision”)?<br>
<br>
#540: parallelism semaphores, Shepherd: Eric <br>
2022-11-08: Assigned to Adam<br>
2022-11-17: Re-assigned to Eric<br>
<br>
<br>
#556: fix signature scoping #448, Shepherd: Richard<br>
2022-11-27: Assigned to Richard<br>
<br>
Cheers,<br>
Joachim<br>
<br>
<br>
<br>
<br>
-- <br>
Joachim Breitner<br>
<a href="mailto:mail@joachim-breitner.de" target="_blank">mail@joachim-breitner.de</a><br>
<a href="http://www.joachim-breitner.de/" rel="noreferrer" target="_blank">http://www.joachim-breitner.de/</a><br>
<br>
_______________________________________________<br>
ghc-steering-committee mailing list<br>
<a href="mailto:ghc-steering-committee@haskell.org" target="_blank">ghc-steering-committee@haskell.org</a><br>
<a href="https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee" rel="noreferrer" target="_blank">https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee</a><br>
</blockquote></div>