Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:124016
Feedback-ID: ifab94697:Fastmail
User-Agent: Cyrus-JMAP/3.11.0-alpha0-538-g1508afaa2-fm-20240616.001-g1508afaa
Precedence: bulk
MIME-Version: 1.0
Message-ID: <90dd3eb6-c7be-4951-a6b6-fd3785ed92e5@app.fastmail.com>
In-Reply-To: 
 <CAMrTa2E=gomoXakUgDJNL_JtOYV2NkRZ_1MUX_fsiuFk8Mq27Q@mail.gmail.com>
References: <b0e1725c-8abb-4b66-a810-ebe7b89d674e@app.fastmail.com>
 <CAMrTa2EPFoV=jA8s7X_mRDWovkbHaB+bNzd5eyp490p4tA7xfA@mail.gmail.com>
 <8dc5393e-b552-465a-9237-9251e8bf1001@app.fastmail.com>
 <CAMrTa2E=gomoXakUgDJNL_JtOYV2NkRZ_1MUX_fsiuFk8Mq27Q@mail.gmail.com>
Date: Sat, 29 Jun 2024 11:15:54 +0200
To: "Jordan LeDoux" <jordan.ledoux@gmail.com>
Cc: internals@lists.php.net
Subject: Re: [PHP-DEV] [RFC] Operator Overrides -- Lite Edition
Content-Type: multipart/alternative;
 boundary=68f3e3d208bb420f8e33c7465dd9e9f5
From: rob@bottled.codes ("Rob Landers")

--68f3e3d208bb420f8e33c7465dd9e9f5
Content-Type: text/plain



On Sat, Jun 29, 2024, at 02:13, Jordan LeDoux wrote:
>>> 4. The `static` distinction is also fairly meaningless, as in PHP there is no situation possible where an operator overload can occur WITHOUT it operating on objects themselves.
>> 
>> For this, that is the wrong approach. The actual behavior is on the type, not the instance. The object instances may not even know their value, they merely represent the value.
> 
> A GMP object instance that does not know its value? What are you even talking about? Can you show me some code explaining what you mean? I had literally months of this argument for the operator overloads RFC, and studied the overload implementations in six other languages as part of writing that RFC, I feel like I understand this topic fairly well. But I do not understand what you are saying here.

A few minutes ago, I sent an email where I accidentally made the code non-static, and I think I see the merit in what you are saying. It felt so natural to use $this that I didn't even realize I was doing it wrong.

So, looking at your RFC and mine, I think this can be improved.

What would you suggest it look like and then we can work backwards from there?
--68f3e3d208bb420f8e33c7465dd9e9f5
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE html><html><head><title></title><style type=3D"text/css">p.Mso=
Normal,p.MsoNoSpacing{margin:0}</style></head><body><div><br></div><div>=
<br></div><div>On Sat, Jun 29, 2024, at 02:13, Jordan LeDoux wrote:<br><=
/div><blockquote type=3D"cite" id=3D"qt" style=3D""><div dir=3D"ltr"><di=
v class=3D"qt-gmail_quote"><blockquote class=3D"qt-gmail_quote" style=3D=
"margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0.8ex;bor=
der-left-width:1px;border-left-style:solid;border-left-color:rgb(204, 20=
4, 204);padding-left:1ex;"><div class=3D"qt-msg3306475242208035808"><div=
><blockquote type=3D"cite" id=3D"qt-m_3306475242208035808qt"><div dir=3D=
"ltr"><div><div>4. The `static` distinction is also fairly meaningless, =
as in PHP there is no situation possible where an operator overload can =
occur WITHOUT it operating on objects themselves.<br></div></div></div><=
/blockquote><div><br></div><div>For this, that is the wrong approach. Th=
e actual behavior is on the type, not the instance. The object instances=
 may not even know their value, they merely represent the value.<br></di=
v></div></div></blockquote><div><br></div><div>A GMP object instance tha=
t does not know its value? What are you even talking about? Can you show=
 me some code explaining what you mean? I had literally months of this a=
rgument for the operator overloads RFC, and studied the overload impleme=
ntations in six other languages as part of writing that RFC, I feel like=
 I understand this topic fairly well. But I do not understand what you a=
re saying here.<br></div></div></div></blockquote><div><br></div><div>A =
few minutes ago, I sent an email where I accidentally made the code non-=
static, and I think I see the merit in what you are saying. It felt so n=
atural to use $this that I didn't even realize I was doing it wrong.<br>=
</div><div><br></div><div>So, looking at your RFC and mine, I think this=
 can be improved.<br></div><div><br></div><div>What would you suggest it=
 look like and then we can work backwards from there?</div></body></html=
>
--68f3e3d208bb420f8e33c7465dd9e9f5--