Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:116751
MIME-Version: 1.0
References: <CAMrTa2FB-EVGq29oLCU8fYkMYi+KsQiEAFv1xxMFO7vnm8e6=Q@mail.gmail.com>
In-Reply-To: <CAMrTa2FB-EVGq29oLCU8fYkMYi+KsQiEAFv1xxMFO7vnm8e6=Q@mail.gmail.com>
Date: Sat, 1 Jan 2022 09:57:24 -0800
Message-ID: <CAMrTa2Gk58T==x27VNa6YOvzUn_T-K9HDKgniSxFrKmDON_bWQ@mail.gmail.com>
To: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="0000000000006398fb05d4890697"
Subject: Re: [RFC] User Defined Operator Overloads (v0.6)
From: jordan.ledoux@gmail.com (Jordan LeDoux)

--0000000000006398fb05d4890697
Content-Type: text/plain; charset="UTF-8"

On Thu, Dec 9, 2021 at 12:11 PM Jordan LeDoux <jordan.ledoux@gmail.com>
wrote:

> Hello internals,
>
> I last brought this RFC up for discussion in August, and there was
> certainly interesting discussion. Since then there have been many
> improvements, and I'd like to re-open discussion on this RFC. I mentioned
> in the first email to the list that I was planning on taking a while before
> approaching a vote, however the RFC is much closer to vote-ready now, and
> I'd like to open discussion with that in mind.
>
> RFC Link: https://wiki.php.net/rfc/user_defined_operator_overloads
>
> There is a patch for this RFC, however the latest commits are not
> playable. It will build, but with various problems which are being worked
> on related to enums. The last playable commit can be found by checking out
> this commit:
>
>
> https://github.com/JordanRL/php-src/commit/e044f53830a9ded19f7c16a9542521601ac3f331
>
> This commit however does not have the enum for operator position described
> in the RFC. It uses a bool instead with true being the left side, and false
> being the right side.
>
> Implementation details still left:
> - There are issues related to opcache/JIT still, so if you want to play
> around with the playable commit disable both.
> - Reflection has not been updated, but the proposed updates necessary are
> described in the RFC.
>
> It is a long RFC, but operator overloads are a complicated topic if done
> correctly. Please review the FAQ section before asking a question, as it
> covers many of the main objections or inquiries to the feature. I'd be
> happy to expand on any of the answers there if prompted however.
>
> Jordan
>

It seems that most of the discussion and questions have happened. As such,
I'll be opening voting on the RFC on January 3rd unless anyone believes
there are further outstanding issues which should be discussed prior.

I've put together a small set of rules for operator overloads, guidelines
for implementations, that the PHP community could use to start learning the
limitations of this feature while the implementation is being finished and
the documentation for PHP.net is being worked on:
https://github.com/JordanRL/operator-overloads-in-php/blob/master/README.md

Jordan

--0000000000006398fb05d4890697--