<div dir="ltr"><div>Hi, <br></div><div><br></div><div>I support acceptance.</div><div><br></div><div>Vitaly<br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">чт, 23 сент. 2021 г. в 00:53, Simon Peyton Jones via ghc-steering-committee <<a href="mailto:ghc-steering-committee@haskell.org">ghc-steering-committee@haskell.org</a>>:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">I'm in favour of #400.<br>
<br>
Simon<br>
<br>
PS: I am leaving Microsoft at the end of November 2021, at which point <a href="mailto:simonpj@microsoft.com" target="_blank">simonpj@microsoft.com</a> will cease to work. Use <a href="mailto:simon.peytonjones@gmail.com" target="_blank">simon.peytonjones@gmail.com</a> instead. (For now, it just forwards to <a href="mailto:simonpj@microsoft.com" target="_blank">simonpj@microsoft.com</a>.)<br>
<br>
| -----Original Message-----<br>
| From: ghc-steering-committee <ghc-steering-committee-<br>
| <a href="mailto:bounces@haskell.org" target="_blank">bounces@haskell.org</a>> On Behalf Of Vladislav Zavialov (int-index)<br>
| Sent: 16 September 2021 17:07<br>
| To: ghc-steering-committee <<a href="mailto:ghc-steering-committee@haskell.org" target="_blank">ghc-steering-committee@haskell.org</a>><br>
| Subject: [ghc-steering-committee] Proposal #400: COMPLETE set<br>
| signatures; rec: accept<br>
| <br>
| Dear Committee,<br>
| <br>
| Proposal #400 "COMPLETE set signatures" by Sebastian Graf has been<br>
| submitted for our consideration.<br>
| <br>
| Read it here:<br>
| <a href="https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgith" rel="noreferrer" target="_blank">https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgith</a><br>
| <a href="http://ub.com" rel="noreferrer" target="_blank">ub.com</a>%2Fsgraf812%2Fghc-proposals%2Fblob%2Fconstrained-complete-<br>
| sigs%2Fproposals%2F0000-complete-set-<br>
| signatures.rst&data=04%7C01%7Csimonpj%<a href="http://40microsoft.com" rel="noreferrer" target="_blank">40microsoft.com</a>%7Cccd12e8010<br>
| 654946877608d9792c1a90%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C63<br>
| 7674053577434736%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV<br>
| 2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=a3j3xlr4FFrJ0%2<br>
| B6gB80Kb%2FQ%2Faxz0uDyb8HYpLYhNEBg%3D&reserved=0<br>
| Discussion here:<br>
| <a href="https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgith" rel="noreferrer" target="_blank">https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgith</a><br>
| <a href="http://ub.com" rel="noreferrer" target="_blank">ub.com</a>%2Fghc-proposals%2Fghc-<br>
| proposals%2Fpull%2F400&data=04%7C01%7Csimonpj%<a href="http://40microsoft.com" rel="noreferrer" target="_blank">40microsoft.com</a>%7Ccc<br>
| d12e8010654946877608d9792c1a90%7C72f988bf86f141af91ab2d7cd011db47%7C1%<br>
| 7C0%7C637674053577434736%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiL<br>
| CJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=WPnozLD<br>
| TtXlaFkUPtyZbzGSn5%2BmpqoTRkRhoy6SJqfg%3D&reserved=0<br>
| <br>
| The proposal presents an alternative treatment for type annotations on<br>
| COMPLETE pragmas. Today one could write<br>
| <br>
| {-# COMPLETE P, Q :: Either #-}<br>
| <br>
| where P and Q are some pattern synonyms. But this isn't even well-<br>
| kinded.<br>
| <br>
| Instead, the author proposes that we ask our users to write<br>
| <br>
| {-# COMPLETE P, Q :: Either l r #-}<br>
| <br>
| By requiring a proper type on the RHS, we also gain the ability to<br>
| talk about more advanced use cases (described in the proposal).<br>
| <br>
| I recommend acceptance. In fact, I learned about the way these<br>
| annotations are treated today only from reading the proposal, and it<br>
| came as a surprise to me. Using proper, well-kinded types there, seems<br>
| like the right thing to do even if we ignore the new use cases it<br>
| enables.<br>
| <br>
| Let me know what you think.<br>
| <br>
| - Vlad<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" rel="noreferrer" target="_blank">https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmail</a><br>
| .<a href="http://haskell.org" rel="noreferrer" target="_blank">haskell.org</a>%2Fcgi-bin%2Fmailman%2Flistinfo%2Fghc-steering-<br>
| committee&data=04%7C01%7Csimonpj%<a href="http://40microsoft.com" rel="noreferrer" target="_blank">40microsoft.com</a>%7Cccd12e801065494<br>
| 6877608d9792c1a90%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C6376740<br>
| 53577434736%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMz<br>
| IiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=VeWjPT7WIwEpivqCypFm<br>
| 5RmWv%2BLTeT%2BmrQUS76UOVPw%3D&reserved=0<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>