<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 12 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#44546A;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#44546A">Haskell already loses people for silly things like its lack of curly braces and semicolons (if only they knew the truth). And it wins people for marginally
silly things like how many parentheses you typically see. So, while this change may be silly in many ways, programmers are a picky bunch and we cannot underestimate the implications of silly annoyances like needing two lines to import “Text” and “T.pack”.
+1 from me.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#44546A"><o:p> </o:p></span></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> Haskell-Cafe [mailto:haskell-cafe-bounces@haskell.org]
<b>On Behalf Of </b>Sven Panne<br>
<b>Sent:</b> Friday, June 5, 2015 5:55 PM<br>
<b>To:</b> haskell-cafe<br>
<b>Subject:</b> Re: [Haskell-cafe] Proposal: Shorter Import Syntax<o:p></o:p></span></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<div>
<p class="MsoNormal">2015-06-05 7:52 GMT+02:00 Malcolm Wallace <<a href="mailto:malcolm.wallace@me.com" target="_blank">malcolm.wallace@me.com</a>>:<o:p></o:p></p>
<p class="MsoNormal">[...] I think there is a burden on the proposer to demonstrate a decent power-to-weight ratio for the change, and saving a few characters at the expense of introducing considerable confusion just does not seem right to me. "The new syntax
does not let us do anything we cannot do now." On the other hand, I could imagine a different import system altogether being attractive, perhaps a higher-order one like ML modules, although someone would have to flesh out the details.<o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Just another +1 to everything Malcolm wrote: IMHO the proposal is just bikeshedding and doesn't really buy us much. Saving a few keystrokes is not a good argument when it comes to language design, see e.g. Perl or the latest additions to
JavaScript. The current syntax might be a bit verbose, but it's easily comprehensible, and the proposal is a bit confusing. I would really welcome some more powerful module system, e.g. in the spirit of ML/OCaml, but not some ad hoc changes to the current
one.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Regarding the grep on Stackage: Here transitive dependencies should be taken into account, so I guess the overall breakage would be much, much higher. A per-module/package grep is basically meaningless.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Finally: Enabling anything by default what might break something is a total no-go, *unless* everybody agrees that the current state of affairs is broken and the new state is much better. Both doesn't hold here. Enabling some things behind
a flag/pragma is OK, time will then tell if the idea is good or not.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Just my 2c,<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> S.<o:p></o:p></p>
</div>
</div>
</div>
</div>
</div>
</body>
</html>