<div dir="ltr"><div class="gmail_default" style="font-family:tahoma,sans-serif">I'm ok with this proposal.  It's mainly about adding new warnings.  <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 Sat, 29 Jan 2022 at 15:41, Vitaly Bragilevsky <<a href="mailto:bravit111@gmail.com">bravit111@gmail.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">Dear Committee,<br>
<br>
Proposal #270 "Support pun-free code" has been resubmitted by Artyom Kuznetsov.<br>
<br>
<a href="https://github.com/ghc-proposals/ghc-proposals/pull/270" rel="noreferrer" target="_blank">https://github.com/ghc-proposals/ghc-proposals/pull/270</a><br>
<br>
<a href="https://github.com/hithroc/ghc-proposals/blob/master/proposals/0000-support-pun-free-code.md" rel="noreferrer" target="_blank">https://github.com/hithroc/ghc-proposals/blob/master/proposals/0000-support-pun-free-code.md</a><br>
<br>
This proposal was heavily revised since Iavor recommended rejection.<br>
As of now, it is quite thin suggesting just a couple of things:<br>
- warnings for the code with panning (understood as using same names<br>
for both types and values)<br>
- a syntax change for import declarations to reflect which names<br>
(types or values) are actually imported when importing from libraries<br>
relied on punning.<br>
<br>
The first change promotes a new style of writing Haskell code without<br>
distinguishing types and values and having a single unified namespace.<br>
We are already on that road anyway and I don't see any reason not to<br>
support this.<br>
<br>
The second change allows using an old style with punning. It could<br>
lead to doubling import declarations, but I don't think that this is<br>
really a problem.<br>
<br>
I think the proposal is mature enough so I recommend acceptance.<br>
<br>
We can also decide on the actual word used in import declarations<br>
(data, value, or pattern). I personally prefer value, but I don't see<br>
this issue as something important.<br>
<br>
Vitaly<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>