<div dir="ltr">I am being nudged to do something with this proposal, but I am not sure what... Is the rest of the committee OK with moving it back "revisions required", and if so what revisions would we like? <div><br></div><div>I would be quite happy if someone else wanted to shephard this. As I mentioned before, I don't have much interest in DH, so I have not followed the really long discussion related to that, and if and how it might relate to #281. </div><div><br></div><div>My recommendation for the moment would be:</div><div> * This seems like a useful feature independent of DH, so it would be nice to come up with a concise notation to use the feature on its own, without worrying about DH.</div><div><br></div><div>Please let me know what you think, as I am not sure what is the committee's stance on the proposal.</div><div><br></div><div>-Iavor</div><div><br></div><div><br></div><div><br></div><div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Feb 18, 2021 at 1:54 PM Simon Peyton Jones <<a href="mailto:simonpj@microsoft.com">simonpj@microsoft.com</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">
<div lang="EN-GB" style="overflow-wrap: break-word;">
<div class="gmail-m_6746982535017041965WordSection1">
<p class="MsoNormal"><span>There has been a broad further discussion.<u></u><u></u></span></p>
<p class="MsoNormal"><span><u></u><u></u></span></p>
<p class="MsoNormal"><span>What we advertise is that, rather that leave a proposal “under committee review”, we will push it back to the author with an invitation to resubmit when the discussion has died down and they feel
ready to submit a proposal, revised in the light of the discussion. That’s different to reject… it means that there is an ongoing debate so it’s not a good time for the committee to make a decision.<u></u><u></u></span></p>
<p class="MsoNormal"><span><br>
Simon<u></u><u></u></span></p>
<p class="MsoNormal"><span><u></u> <u></u></span></p>
<div style="border-top:none;border-right:none;border-bottom:none;border-left:1.5pt solid blue;padding:0cm 0cm 0cm 4pt">
<div>
<div style="border-right:none;border-bottom:none;border-left:none;border-top:1pt solid rgb(225,225,225);padding:3pt 0cm 0cm">
<p class="MsoNormal"><b><span lang="EN-US">From:</span></b><span lang="EN-US"> ghc-steering-committee <<a href="mailto:ghc-steering-committee-bounces@haskell.org" target="_blank">ghc-steering-committee-bounces@haskell.org</a>>
<b>On Behalf Of </b>Iavor Diatchki<br>
<b>Sent:</b> 18 February 2021 16:47<br>
<b>To:</b> Joachim Breitner <<a href="mailto:mail@joachim-breitner.de" target="_blank">mail@joachim-breitner.de</a>><br>
<b>Cc:</b> ghc-steering-committee <<a href="mailto:ghc-steering-committee@haskell.org" target="_blank">ghc-steering-committee@haskell.org</a>><br>
<b>Subject:</b> Re: [ghc-steering-committee] Status<u></u><u></u></span></p>
</div>
</div>
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<p class="MsoNormal" style="margin-right:0cm;margin-bottom:6pt;margin-left:0cm">
On #381 I think the idea of visible quantification makes sense every now and then, but I don't like the concrete details of the proposal: the magic lifting of terms to types seems quite complicated, and using `type` as an explicit herald doesn't look nice.
So I don't think it's the right design, and therefore I suggest we reject the proposal.<u></u><u></u></p>
<div>
<p class="MsoNormal" style="margin-right:0cm;margin-bottom:6pt;margin-left:0cm">
<u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal" style="margin-right:0cm;margin-bottom:6pt;margin-left:0cm">
I am sure that others would disagree as apparently this is an essential part of dependent Haskell. I have not followed the large discussion that Richard created, as I am not particularly interested in the design being proposed, so perhaps someone else should
champion this.<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal" style="margin-right:0cm;margin-bottom:6pt;margin-left:0cm">
<u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal" style="margin-right:0cm;margin-bottom:6pt;margin-left:0cm">
Aslo, I am not sure if I am actually on the committee, as I thought my term had expired? That might be more reason for someone else to pick it up.<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal" style="margin-right:0cm;margin-bottom:6pt;margin-left:0cm">
<u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal" style="margin-right:0cm;margin-bottom:6pt;margin-left:0cm">
-Iavor<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal" style="margin-right:0cm;margin-bottom:6pt;margin-left:0cm">
<u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal" style="margin-right:0cm;margin-bottom:6pt;margin-left:0cm">
<u></u> <u></u></p>
</div>
</div>
<p class="MsoNormal" style="margin-right:0cm;margin-bottom:6pt;margin-left:0cm">
<u></u> <u></u></p>
<div>
<div>
<p class="MsoNormal" style="margin-right:0cm;margin-bottom:6pt;margin-left:0cm">
On Thu, Feb 18, 2021 at 2:32 AM Joachim Breitner <<a href="mailto:mail@joachim-breitner.de" target="_blank">mail@joachim-breitner.de</a>> wrote:<u></u><u></u></p>
</div>
<blockquote style="border-top:none;border-right:none;border-bottom:none;border-left:1pt solid rgb(204,204,204);padding:0cm 0cm 0cm 6pt;margin-left:4.8pt;margin-right:0cm">
<p class="MsoNormal" style="margin-right:0cm;margin-bottom:6pt;margin-left:0cm">
Dear Committee,<br>
<br>
another status update, because why not.<br>
<br>
A small reminder: These mails have two sections, one that’s a delta<br>
since last status, but below is a summary of all proposals we have to<br>
act on. Please at least scroll through that on each status mail to see<br>
if you are listed, maybe you forgot something (or I made a mistake).<br>
<br>
So here’s the delta since last month.<br>
<br>
* GHC2021 defined! Yay!<br>
<br>
* Bylaws merged! Yay<br>
<br>
* Simon², Iavor, Richard and me had thus their terms expired.<br>
<br>
The Simons, as key members, wanted to continue and were<br>
voted back in.<br>
<br>
The others are now “expiring”, until the next nomination round<br>
concludes. Alejandro is going to run that process.<br>
<br>
* we were asked to review these proposals:<br>
#390: Fine-grained pragmas, Shepherd: Vitaly<br>
<br>
* we have a recommendation from the shepherd about:<br>
#368: Warn on prefix/suffix operators (accept)<br>
<br>
* we have sent the following proposals back to revision<br>
- none -<br>
<br>
* we decided about the following proposals<br>
#313: Delimited continuation primops (accept)<br>
#387: The Char kind (accept)<br>
#368: Warn on prefix/suffix operators (accept)<br>
<br>
We currently have to act on the following 5 proposals, down by 2.<br>
<br>
## Waiting for committee decision<br>
<br>
#381: Visible 'forall' in types of terms, Shepherd: Iavor<br>
Recommendation was to reject, but discussion went into the more <br>
abstract “whither dependent Haskell”. But what does this mean<br>
for this proposal?<br>
Iavor, can you pick this up again?<br>
<br>
#369: Add sumToTag# primop, Shepherd: Eric<br>
Essentially accepted, waiting for feedback from the author on<br>
final tweaks. Eric, care to nudge the author, or just do it?<br>
<br>
#302: \of, Shepherd: Cale<br>
No new discussion yet. It seems there was some confusion, which<br>
was cleared up by Tom, and Cale said he’ll pick it up now again.<br>
<br>
<br>
## Waiting for Shepherd action<br>
<br>
#367: Clarify primops using unboxed sums, Shepherd: Simon Marlow<br>
Simon said he’d reject it on the Github PR. Still waiting<br>
for the discussion to start on the mailing list.<br>
<br>
#390: Fine-grained pragmas, Shepherd: Vitaly<br>
Still kinda new, but a recommendation would be good soon.<br>
<br>
<br>
Cheers,<br>
Joachim<br>
-- <br>
Joachim Breitner<br>
<a href="mailto:mail@joachim-breitner.de" target="_blank">mail@joachim-breitner.de</a><br>
<a href="https://nam06.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.joachim-breitner.de%2F&data=04%7C01%7Csimonpj%40microsoft.com%7Cbc1da190b85a4cf21e4b08d8d42ceb8e%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637492636704547033%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000&sdata=5wTbz6wc4abeqyC3TXDU2O8kftB9Rwz1dHnkXM%2FGErE%3D&reserved=0" target="_blank">
http://www.joachim-breitner.de/</a><br>
<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://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmail.haskell.org%2Fcgi-bin%2Fmailman%2Flistinfo%2Fghc-steering-committee&data=04%7C01%7Csimonpj%40microsoft.com%7Cbc1da190b85a4cf21e4b08d8d42ceb8e%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637492636704557030%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000&sdata=0MJhOYvjonZABu01LyVUN2zqOKC3xqf5qEidT8d%2B2os%3D&reserved=0" target="_blank">https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee</a><u></u><u></u></p>
</blockquote>
</div>
</div>
</div>
</div>
</blockquote></div>