[ghc-steering-committee] Record dot syntax: vote results

Vitaly Bragilevsky bravit111 at gmail.com
Wed Apr 1 16:48:55 UTC 2020


Well, this was not a problem 30 years ago:
[image: 2020-04-01 19.45.59.jpg]

Vitaly

ср, 1 апр. 2020 г. в 12:44, Richard Eisenberg <rae at richarde.dev>:

> Small note: It sounds like we're getting ready to wrap this up with that
> post of Simon's on GitHub. Might I humbly suggest we wait one more day?
> Declaring the committee's vote today, April 1, might only sow confusion. :)
>
> Richard
>
> On Apr 1, 2020, at 7:00 AM, Alejandro Serrano Mena <trupill at gmail.com>
> wrote:
>
>
>
> El mié., 1 abr. 2020 a las 0:09, Iavor Diatchki (<iavor.diatchki at gmail.com>)
> escribió:
>
>> Hello,
>>
>>    - Indeed, you could write some expressions that might look confusing
>> at first, but I don't see why would you?  After all, one could use the
>> exact same argument for many other notations in pretty much any programming
>> language (e.g., operator precedences can be used to write confusing
>> code---it doesn't mean that they are not very useful sometime).
>>
>
> But I think it's important to think also of potentially confusing type
> errors which may arise if we allow such freedom. I find easier to simply
> say "f r .x" cannot be parsed, and then asking the user to disambiguate
> between "(f r).x" or "f r.x" than to allow it in the parser and then obtain
> a huge error message.
>
> Part of the reason why I'm so concerned about it is that my prediction is
> that this is not "just" any other extension. Many people, including
> beginners, will enable this by default, since it makes one slightly alien
> part of Haskell (field access) look like what they might be used to.
>
>
> _______________________________________________
> ghc-steering-committee mailing list
> ghc-steering-committee at haskell.org
> https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.haskell.org/pipermail/ghc-steering-committee/attachments/20200401/3a27376d/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 2020-04-01 19.45.59.jpg
Type: image/jpeg
Size: 24209 bytes
Desc: not available
URL: <http://mail.haskell.org/pipermail/ghc-steering-committee/attachments/20200401/3a27376d/attachment-0001.jpg>


More information about the ghc-steering-committee mailing list