Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:107877
To: "internals@lists.php.net" <internals@lists.php.net>
Thread-Topic: Opt-in "use function *;" for skipping check for function/const
 in alternate namespace 
Thread-Index: AQHVpX6vrwD1LJEJ30mFfcAOFan0sA==
Date: Thu, 28 Nov 2019 00:02:12 +0000
Message-ID:
 <DM6PR07MB45536166C2939FF19F496893F9440@DM6PR07MB4553.namprd07.prod.outlook.com>
Accept-Language: en-CA, en-US
Content-Language: en-CA
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-RMS-PersistedConsumerOrg: 00000000-0000-0000-0000-000000000000
X-MS-Exchange-CrossTenant-Network-Message-Id: ca0611a9-5351-4c57-e540-08d773963881
X-MS-Exchange-CrossTenant-rms-persistedconsumerorg: 00000000-0000-0000-0000-000000000000
X-MS-Exchange-CrossTenant-originalarrivaltime: 28 Nov 2019 00:02:12.5160
 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Internet
X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN3NAM04HT104
X-Envelope-From: <tysonandre775@hotmail.com>
Subject: Opt-in "use function *;" for skipping check for function/const in
 alternate namespace
From: tysonandre775@hotmail.com (tyson andre)


What are your thoughts about syntax such as the following, similar to the s=
yntax for Java (only for use of functions/constants from the root scope)=0A=
=0A=
<?php=0A=
namespace My\NS;=0A=
use function *;=0A=
use const *;=0A=
// can use functions/constants from namespaces that aren't the global names=
pace to override '*'=0A=
// "use *" is not valid.=0A=
printf("PHP Version is: %s\n", PHP_VERSION);=0A=
=0A=
A similar opt-in directive syntax "use function root;" was mentioned as an =
alternative to the "Deprecation of fallback to root scope" RFC https://marc=
.info/?l=3Dphp-internals&m=3D151788196501507&w=3D2 . (I couldn't find any o=
ther mentions after a quick search)=0A=
=0A=
Benefits of "use function *":=0A=
- Visually cleaner and less prone to merge conflicts than "use" for dozens =
of functions/constants all from the root scope. (or writing \printf("PHP Ve=
rsion is: %s\n", \PHP_VERSION), or mixes of the above)=0A=
- Due to the absence of function autoloading (not supported in php to perfo=
rmance overhead), functions outside the global scope are rare in practice.=
=0A=
- This would make it easier to make edits to a project (if the project's co=
de style involves the unambiguous use of functions/global constants)=0A=
- This makes using unambiguous functions/global constants easier. (for a sm=
all performance boost due to the php interpreter not needing to check both =
namespaces, opcache knowing exactly which function/constant it is, etc)=0A=
- Does not break third-party code=0A=
=0A=
The other RFC https://wiki.php.net/rfc/fallback-to-root-scope-deprecation h=
ad the following notable objections, and I'm not sure of the current status=
 of it:=0A=
=0A=
- Deprecating the behavior of existing code would break (possibly unmaintai=
ned) third-party libraries and require a lot of code changes, discouraging =
updates=0A=
=0A=
   "use function *;" wouldn't.=0A=
- Some mocking libraries will declare functions in namespaces being tested,=
 with the same name as the global function.=0A=
  My proposal has similar drawbacks - third party code that started using "=
use function *" would break those libraries (but so would manually adding t=
he same namespace uses).=0A=
=0A=
  But there are alternatives to those libraries, such as uopz, runkit7, and=
 SoftMocks (SoftMocks changes the class autoloader to replace code with ins=
trumented code).=0A=
=0A=