[ghc-steering-committee] #380 GHC2021: Voting starts

Alejandro Serrano Mena trupill at gmail.com
Sun Nov 29 20:14:47 UTC 2020


El dom, 29 nov 2020 a las 12:12, Simon Marlow (<marlowsd at gmail.com>)
escribió:

> On Wed, 25 Nov 2020 at 11:21, Spiwack, Arnaud <arnaud.spiwack at tweag.io>
> wrote:
>
>>
>> ## OverloadedX
>>
>> These extensions can confuse type inference, yielding ambiguous type
>> variables message. And as much as I like them, I don't think it's safe
>> to include them yet. Not until we have a reasonable story for
>> defaulting literals.
>>
>> OverloadedLabels: no
>> OverloadedLists: no
>> OverloadedStrings: no
>>
>
> For what it's worth, I've been writing code with OverloadedStrings for
> several years now and in my experience it rarely causes a problem, even for
> beginners. The context almost always provides enough information to resolve
> the ambiguity. (admittedly I'm slightly surprised by this too, but
> experience has convinced me)
>
> I don't have much experience with OverloadedLists, but I'd be prepared to
> believe that it's a similar story there too.
>

Adding to this, I think that both OverloadedStrings and OverloadedLists go
very well with the idea of overloaded literals story that Haskell already
has for numbers.

Regards,
Alejandro


> OverloadedLabels is really a new syntactic form and doesn't fall into the
> same category as the other two here.
>
> Cheers
> 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/20201129/0e79466d/attachment.html>


More information about the ghc-steering-committee mailing list