Thanks. So can you explain why other languages (like D) have UFCS? How do
they solve these problems? Or do they simply not care about them?

On Mon, Sep 12, 2022 at 10:04 PM Ville Voutilainen <
ville.voutilainen_at_[hidden]> wrote:

> On Mon, 12 Sept 2022 at 15:49, blacktea hamburger via Std-Proposals
> <std-proposals_at_[hidden]> wrote:
> >
> > I think adding new features requires trade-offs. Users need to become
> more careful, but that's not too hard. More importantly, it brings many
> benefits.
>
> It's splendidly hard, when a facility that has, since the dawn of
> time, formed a closed overload set now becomes a facility
> that forms an open overload set. API designers could no longer protect
> their users from the downsides, whereas now they
> can, and they can be confident that the protection stays in place over
> time, over refactorings elsewhere.
>
> The benefits are not worth losing such a large-scale semantic
> guarantee API-design-wise. "Users need to become more careful"
> is directly at odds with "the language provides facilities that help
> writing large-scale programs".
>