<div dir="ltr">I think that `f x.y` should mean `f (x.y)`.</div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Dec 12, 2019 at 6:00 AM 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>
Am Donnerstag, den 12.12.2019, 12:30 +0000 schrieb Richard Eisenberg:<br>
> I would also like to propose<br>
> <br>
> (C). Syntax error.<br>
> <br>
> That is, a tight-infix use of `.` does not associate with a function application on its left. A prefix occurrence of `.` would: `f x .y` would be `(f x) .y`.<br>
> <br>
> <br>
> We could also just make this a warning.<br>
<br>
such a warning was actually also proposed in the monster GitHub thread:<br>
<a href="https://github.com/ghc-proposals/ghc-proposals/pull/282#issuecomment-564597503" rel="noreferrer" target="_blank">https://github.com/ghc-proposals/ghc-proposals/pull/282#issuecomment-564597503</a><br>
as -Wproximity, which could warn about any misleading spacing, so not only<br>
`f x.y` (whether this is a record access or function composition), but also<br>
`x * y+z` etc.<br>
<br>
Sounds very nice! Probably orthogonal to this proposal, but maybe a way<br>
to make people worry less about the confusion that `f x.y` may bring?<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>
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>