Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:107879
MIME-Version: 1.0
References: <DM6PR07MB45536166C2939FF19F496893F9440@DM6PR07MB4553.namprd07.prod.outlook.com>
In-Reply-To: <DM6PR07MB45536166C2939FF19F496893F9440@DM6PR07MB4553.namprd07.prod.outlook.com>
Date: Thu, 28 Nov 2019 09:35:27 +0000
Message-ID: <CALKiJKo3eeyM51AB0o+nph2WfkNWaJ8tQp1h23ETencJXzE+Dw@mail.gmail.com>
To: "internals@lists.php.net" <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000fe7efd059864d567"
Subject: Re: [PHP-DEV] Opt-in "use function *;" for skipping check for
 function/const in alternate namespace
From: rowan.collins@gmail.com (Rowan Tommins)

--000000000000fe7efd059864d567
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Thu, 28 Nov 2019 at 00:02, tyson andre <tysonandre775@hotmail.com> wrote=
:

> - Due to the absence of function autoloading (not supported in php to
> performance overhead), functions outside the global scope are rare in
> practice.
>


If this is a valid justification, perhaps we should do the opposite of the
"deprecate fallback to global scope" RFC you mentioned, and make the "use
function *" behaviour the default in some future version. That would
provide us longer term benefits, such as being able to introduce function
autoloading.

An opt-in mechanism is certainly easier to migrate to, but it would be a
shame if every PHP file in 10 years time included a line like this:

use function *; // don't know what this does, but apparently it's good for
performance =C2=AF\_(=E3=83=84)_/=C2=AF

Regards,
--=20
Rowan Tommins
[IMSoP]

--000000000000fe7efd059864d567--