Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:125411
Feedback-ID: ifab94697:Fastmail
Precedence: bulk
MIME-Version: 1.0
Date: Tue, 03 Sep 2024 23:44:51 +0200
To: internals@lists.php.net
Message-ID: <df217c26-cb23-46d6-b931-431c8971599c@app.fastmail.com>
In-Reply-To: <2716f729-4008-4f75-8412-861d8960b746@app.fastmail.com>
References: <2716f729-4008-4f75-8412-861d8960b746@app.fastmail.com>
Subject: Re: [PHP-DEV] function autoloading v4 RFC
Content-Type: multipart/alternative;
 boundary=cf37833f06c446d08ea1ed533dfe303b
From: rob@bottled.codes ("Rob Landers")

--cf37833f06c446d08ea1ed533dfe303b
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

On Thu, Aug 15, 2024, at 17:22, Rob Landers wrote:
> Hello internals,
>=20
> I've decided to attempt an RFC for function autoloading. After reading=
 hundreds of ancient (and recent) emails relating to the topic along wit=
h several abandoned RFCs from the past, and after much review, I've deci=
ded to put forth a variation of a previous RFC, as it seemed the least a=
mbitious and the most likely to work:
>=20
> https://wiki.php.net/rfc/function_autoloading4
>=20
> Please let me know what you think. An implementation should be along b=
efore opening it for a vote (now that I realize how important that is).
>=20
> =E2=80=94 Rob

Hello internals,

I've updated the RFC text and clarified some language (hopefully) while =
also addressing a number of concerns.
 1.  I've removed the BC break=E2=80=94the 'type' of the autoloadee will=
 not be passed to the autoloader. This can allow someone to use spl_auto=
load for function autoloading if they so desire.
 2. I've removed artificial restrictions on the constants in which all f=
unctions that take them can accept both at the same time and behave appr=
opriately.
 3. I've performed multiple benchmarks on several projects (WordPress, S=
ymfony, and others from techempower) and couldn't detect a statistically=
 significant performance difference with this feature in multiple config=
urations.
 4. Some simplified aspects of Gina's implementation for core autoloadin=
g were integrated into the patch. However, I see that RFC as a general r=
efactoring of the API more than function autoloading. This RFC is strict=
ly about function autoloading while being very conservative with the aut=
oloading API.
While minor issues in the PR are still being worked on, I plan to open t=
he vote next Wednesday, September 11th 2024, barring any significant pus=
hback or objections.

=E2=80=94 Rob
--cf37833f06c446d08ea1ed533dfe303b
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE html><html><head><title></title><style type=3D"text/css">=0Ap.=
MsoNormal,p.MsoNoSpacing{margin:0}</style></head><body><div><font>On Thu=
, Aug 15, 2024, at 17:22, Rob Landers wrote:</font><br></div><blockquote=
 type=3D"cite" id=3D"qt" style=3D""><div><font>Hello internals,</font><b=
r></div><div><br></div><div><font>I've decided to attempt an RFC for fun=
ction autoloading. After reading hundreds of ancient (and recent) emails=
 relating to the topic along with several abandoned RFCs from the past, =
and after much review, I've decided to put forth a variation of a previo=
us RFC, as it seemed the least ambitious and the most likely to work:</f=
ont><br></div><div><br></div><div><a href=3D"https://wiki.php.net/rfc/fu=
nction_autoloading4">https://wiki.php.net/rfc/function_autoloading4</a><=
br></div><div><br></div><div><font>Please let me know what you think. An=
 implementation should be along before opening it for a vote (now that I=
 realize how important that is).</font><br></div><div><br></div><div id=3D=
"qt-sig121229152"><font>=E2=80=94 Rob</font><br></div></blockquote><div>=
<br></div><div>Hello internals,<br></div><div><br></div><div><font>I've =
updated the RFC text and clarified some language (hopefully) while also =
addressing a number of concerns.</font><br></div><ol><li><font>&nbsp;I'v=
e removed the BC break=E2=80=94the 'type' of the autoloadee will not be =
passed to the autoloader. This can allow someone to use spl_autoload for=
 function autoloading if they so desire.</font><br></li><li><font>I've r=
emoved artificial restrictions on the constants in which all functions t=
hat take them can accept both at the same time and behave appropriately.=
</font><br></li><li><font>I've performed multiple benchmarks on several =
projects (WordPress, Symfony, and others from techempower) and couldn't =
detect a statistically significant performance difference with this feat=
ure in multiple configurations.</font><br></li><li><font>Some simplified=
 aspects of Gina's implementation for core autoloading were integrated i=
nto the patch. However, I see that RFC as a general refactoring of the A=
PI more than function autoloading. This RFC is strictly about function a=
utoloading while being very conservative with the autoloading API.</font=
><br></li></ol><div>While minor issues in the PR are still being worked =
on, I plan to open the vote next Wednesday, September 11th 2024, barring=
 any significant pushback or objections.</div><div><br></div><div id=3D"=
sig121229152"><font>=E2=80=94 Rob</font><br></div></body></html>
--cf37833f06c446d08ea1ed533dfe303b--