On Tue, Mar 22, 2022 at 10:31 AM Christian Schneider <cschn...@cschneid.com> wrote:
> Am 22.03.2022 um 16:14 schrieb Sara Golemon <poll...@php.net>: > > So while I said I wanted to avoid the firestorm suggesting userspace > > overloading would bring, maybe that's the question to ask: > > > > Who's just a hard-nope on userspace operator overloading? If your > reasons > > go beyond foot-gun (and that is a valid reason), could you share what > those > > reasons are? > > > An obvious one could be complexity. > > In the discussion about warning in conjunction with type juggling it was > mentioned that this leads to increased complexity in the PHP core. While my > knowledge of the engine is too superficial to really know I'd assume that > generic operator overload could lead to quite some additional complexity > and/or overhead. > > I'm not terribly worried about complexity since operator overloading *already* exists in the engine. The only thing we don't have is a little bit of glue to map these out to method calls. This would be best served by actually writing up an implementation, which I may do yet, but at the moment, I'm just gathering opinions. -Sara
