Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:109263
MIME-Version: 1.0
References: <003701d6013c$9afe9750$d0fbc5f0$@gmx.de>
In-Reply-To: <003701d6013c$9afe9750$d0fbc5f0$@gmx.de>
Date: Tue, 24 Mar 2020 11:03:46 +0100
Message-ID: <CADyq6sKPNgTYw9gVc16v1=Ysc3F+MDJgL7P7Q5gE7fcCXBu8Kg@mail.gmail.com>
To: jan.h.boehmer@gmx.de
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000bd1cf505a196de3e"
Subject: Re: [PHP-DEV] [VOTE] Userspace operator overloading
From: ocramius@gmail.com (Marco Pivetta)

--000000000000bd1cf505a196de3e
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hey Jan,

Just posting here why I voted "no": it is not your implementation proposal,
but rather the concept per-se that IMO shouldn't land in the language.

Operator overloading makes call-site code reading extremely hard, and it
makes the language much more complex for very little benefit.

Everything suggested in the RFC can be done by using explicit arrows: `->`
(method calls), which lead to expressively named methods and parameters.

I have posted similar thoughts about `->__toString()` and `->toString()`
when it comes to cast operations vs explicit calls at
https://github.com/ShittySoft/symfony-live-berlin-2018-doctrine-tutorial/pu=
ll/3#issuecomment-460441229

Overall, without type classes and infix functions, operator overloading is,
IMO, just messy.

Greets,

Marco Pivetta

http://twitter.com/Ocramius

http://ocramius.github.com/


On Mon, Mar 23, 2020 at 6:58 PM <jan.h.boehmer@gmx.de> wrote:

> Hi internals,
>
> I have opened voting on
> https://wiki.php.net/rfc/userspace_operator_overloading, which allows
> users
> to overload operators in their own classes.
>
> Voting closes on 2020-04-06.
>
> Regards,
> Jan B=C3=B6hmer
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>

--000000000000bd1cf505a196de3e--