[ghc-steering-committee] Fwd: Proposal #606: small syntax change around types in terms; recommendation: vote

[Richard Eisenberg]

I remain unmoved by Simon's example. The status quo is already simple:
`type` extends as far to the right as possible. Just like \. And just like
`do`, `else`, and `in`.

The hope is that people using this will tend to avoid punning, and so the
matter will be moot, anyway.

Richard

On Thu, Jan 25, 2024 at 7:08 AM Simon Peyton Jones <
simon.peytonjones at gmail.com> wrote:

> I vote (2), fairly strongly
>
> Remember this comment from Vlad:
>
> @phadej <https://github.com/phadej> For what it's worth, this was my
>> initial thinking when I put ktype there, so past me agrees with you.
>> What changed my opinion is that two years later (i.e. now) I looked at the
>> examples like *fn (type Int -> [a])* and had to double check the
>> specification if it was supposed to be fn ((type Int) -> [a]) or fn
>> (type (Int -> [a])).
>
>
> The point is that the `type` namespace changer can appear *deep within a
> type*.  It's not like "@"!    For exmaple
> fn ((type K) -> [a])
> makes perfect sense.  fn has a required type argument, but in the (type K) *sub-part
> *of the type do we switch to the type namespace.  (Maybe K is in scope
> also as a data constructor.)  Without the parens, do you really want to
> wonder about how this parses?
> fn (type K -> [a])
>
> I prefer code that is slightly longer, but much clearer, than saving two
> characters but requiring reference to the user manual to parse.
>
> Let's make it simple and unambiguous for now.  If it seems painful in
> practice we can debate liberalising it.
>
> Simon
> _______________________________________________
> 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/20240125/865b0296/attachment.html>