<div dir="ltr"><div class="markdown-here-wrapper" style=""><p style="margin:0px 0px 1.2em!important">I’m rather uncomfortable with (1), for reasons mentioned by others before: it prevents cutting a sequence of <code style="font-size:0.85em;font-family:Consolas,Inconsolata,Courier,monospace;margin:0px 0.15em;padding:0px 0.3em;white-space:pre-wrap;border:1px solid rgb(234,234,234);background-color:rgb(248,248,248);border-radius:3px;display:inline">.field</code> with a newline.</p>
<p style="margin:0px 0px 1.2em!important">I’m agnostic between (2) and (3).</p>
<p style="margin:0px 0px 1.2em!important">I’m fine with a vote, but even more fine with Simon just choosing for everybody else :) .</p>
<div title="MDH:PGRpdj5JJ20gcmF0aGVyIHVuY29tZm9ydGFibGUgd2l0aCAoMSksIGZvciByZWFzb25zIG1lbnRp
b25lZCBieSBvdGhlcnMgYmVmb3JlOiBpdCBwcmV2ZW50cyBjdXR0aW5nIGEgc2VxdWVuY2Ugb2Yg
YC5maWVsZGAgd2l0aCBhIG5ld2xpbmUuPC9kaXY+PGRpdj48YnI+PC9kaXY+PGRpdj5JJ20gYWdu
b3N0aWMgYmV0d2VlbiAoMikgYW5kICgzKS48L2Rpdj48ZGl2Pjxicj48L2Rpdj48ZGl2PkknbSBm
aW5lIHdpdGggYSB2b3RlLCBidXQgZXZlbiBtb3JlIGZpbmUgd2l0aCBTaW1vbiBqdXN0IGNob29z
aW5nIGZvciBldmVyeWJvZHkgZWxzZSA6KSAuPGJyPjwvZGl2Pg==" style="height:0;width:0;max-height:0;max-width:0;overflow:hidden;font-size:0em;padding:0;margin:0"></div></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Jan 7, 2020 at 1:50 PM 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">Hi,<br>
<br>
I dislike separating the two major questions.<br>
<br>
If we go with (3) (tight postfix, Ocaml-style), the no-space question<br>
becomes irrelevant; we’d not even have to mention it any more, as it<br>
follows naturally from tight binding.<br>
<br>
If we go with (2) (same-as-application, JS-style), then the no-space<br>
question becomes “do we want to make zero whitespace special”.<br>
<br>
<br>
So to me, the two questions are inherently tied together.<br>
<br>
<br>
If it comes to a vote, that’s not a problem; ranked voting will take<br>
care of that.<br>
<br>
<br>
Views have been exchanged, no new technical insights have appeared for<br>
a while and this is inherently opinion-based, so I am inclined to just<br>
resolve this by voting among the committee, instead of poking until<br>
consensus emerges.<br>
<br>
Cheers,<br>
Joachim<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>
_______________________________________________<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>