Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:125116
Precedence: bulk
MIME-Version: 1.0
References: <1b59392a-68cb-36eb-0fef-977ac7113520@php.net>
In-Reply-To: <1b59392a-68cb-36eb-0fef-977ac7113520@php.net>
Date: Fri, 23 Aug 2024 11:58:29 +0200
Message-ID: <CADU7aosqinbQODpoqGADFhr6cx=1HEsdG+9O=JbiKs15qAjcRA@mail.gmail.com>
Subject: Re: [PHP-DEV] State of Generics and Collections
To: Derick Rethans <derick@php.net>
Cc: PHP Developers Mailing List <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000e2199c062056d1f1"
From: kevin@dunglas.fr (=?UTF-8?Q?K=C3=A9vin_Dunglas?=)

--000000000000e2199c062056d1f1
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Thanks for sharing this research work.

Instead of having to choose between fully reified generics and erased type
declarations, couldn't we have both? A new option in php.ini could allow to
enable the =E2=80=9Cerased=E2=80=9D mode as a performance, production-orien=
ted optimization.
In development, and on projects where performance isn't critical, types
(including generics) will be enforced at runtime, but users will have the
option of opting to disable these checks for production environments.

If this is not possible, the inline caches presented in the article,
combined with =E2=80=9Cworker=E2=80=9D runtimes such as FrankenPHP, Swoole,=
 RoadRunner,
etc., could make the cost of enforcing generics negligible: technically,
types will be computed once and reused for many HTTP requests (because they
are handled by the same long-running PHP script under the hood). As working
runtimes already provide a significant performance improvement over FPM, we
could say that even if non-performance-critical applications (most
applications) will be a bit slower because of the new checks,  people
working on performance-sensitive applications will have the opportunity to
reduce the cost of checks to virtually nothing by switching to a
performance-oriented runtime.

Cheers,

--000000000000e2199c062056d1f1
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_quote"><div></div><div>Thanks for shar=
ing this research work.<br><br>Instead of having to choose between fully re=
ified generics and erased type declarations, couldn&#39;t we have both? A n=
ew option in php.ini could allow to enable the =E2=80=9Cerased=E2=80=9D mod=
e as a performance, production-oriented optimization.<br>In development, an=
d on projects where performance isn&#39;t critical, types (including generi=
cs) will be enforced at runtime, but users will have the option of opting t=
o disable these checks for production environments.<br><br>If this is not p=
ossible, the inline caches presented in the article, combined with =E2=80=
=9Cworker=E2=80=9D runtimes such as FrankenPHP, Swoole, RoadRunner, etc., c=
ould make the cost of enforcing generics negligible: technically, types wil=
l be computed once and reused for many HTTP requests (because they are hand=
led by the same long-running PHP script under the hood). As working runtime=
s already provide a significant performance improvement over FPM, we could =
say that even if non-performance-critical applications (most applications) =
will be a bit slower because of the new checks, =C2=A0people working on per=
formance-sensitive applications will have the opportunity to reduce the cos=
t of checks to virtually nothing by switching to a performance-oriented run=
time.<br></div><div><br></div><div>Cheers, <br></div></div></div>

--000000000000e2199c062056d1f1--