Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:116778
User-Agent: Cyrus-JMAP/3.5.0-alpha0-4525-g8883000b21-fm-20211221.001-g8883000b
Mime-Version: 1.0
Message-ID: <e0358c86-622e-4347-a36c-2e8e16759004@www.fastmail.com>
In-Reply-To: <3225c921-9b26-d2e0-f76f-45fff6f5a12a@processus.org>
References: 
 <CAMrTa2Emxro81j7UMA5QZ+wCOY7g46LSotLRD4oUG7HEfqSD0A@mail.gmail.com>
 <CADyq6sKP6fztfF54e_VTHJRMcB8b0_TahMTTY0hw8LAgciY61w@mail.gmail.com>
 <CAB-BujZB31Ccw6nhN9PG1-VDqt8YkijsYUBYPxJ-Ss1Ng4KJ+w@mail.gmail.com>
 <CADyq6sLh+e74qeMrOuX1_PdN40Jw7m=3wMGMmdF-rwXkJLS1mg@mail.gmail.com>
 <3225c921-9b26-d2e0-f76f-45fff6f5a12a@processus.org>
Date: Mon, 03 Jan 2022 10:12:12 -0600
To: "php internals" <internals@lists.php.net>
Content-Type: text/plain
Subject: Re: [PHP-DEV] [VOTE] User Defined Operator Overloads
From: larry@garfieldtech.com ("Larry Garfield")

On Mon, Jan 3, 2022, at 9:52 AM, Pierre wrote:

> I personally tend to agree with everything that Marco said. Especially 
> regarding the fact that it's adding huge complexity to the language 
> itself for mostly edge cases.
>
> I'd argue there's many much more valuable features that could be added 
> to PHP before operator overload, such as generics, rationalized 
> collection API and scalar objects with methods for example (which all 
> could be magnificent tools for improving the operator overload RFC).

Those are all independent of operator overloading.  There's zero reason one needs to come before/after any other.  Everyone wants generics, but they're really hard or Nikita would have implemented them already.  This is a non-argument.

Also, people keep talking about edge cases.  In my experience, "are these two objects equal" (for some object-specific definition of equal) is very much *not* an edge case.  I may have less use for overloading % as I don't use advanced math that much, but I compare things all the frickin' time and that would be incredibly useful day to day.

--Larry Garfield