Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:110226
To: Dan Ackroyd <Danack@basereality.com>, PHP internals
	<internals@lists.php.net>
Thread-Topic: [PHP-DEV] Draft RFC callable types + callable type/function
 autoloading
Thread-Index: AQHWLqax3x5+HtXHVUmJCdckAxA+maixscdx
Date: Thu, 21 May 2020 01:28:04 +0000
Message-ID:
 <DM6PR07MB66186CD0CDBF1EA48AC4179DF9B70@DM6PR07MB6618.namprd07.prod.outlook.com>
References:
 <CA+kxMuRg14XXiYOrDvWygAs+a+mFd2-skYLO6yddnj+9+4w6pw@mail.gmail.com>
In-Reply-To:
 <CA+kxMuRg14XXiYOrDvWygAs+a+mFd2-skYLO6yddnj+9+4w6pw@mail.gmail.com>
Accept-Language: en-CA, en-US
Content-Language: en-CA
x-ms-exchange-messagesentrepresentingtype: 1
x-tmn: [FsWGCsp+gJtB33aCWnW1JJZ5FGibQMtVa66yBMXkA7+FdRHaRBrKxBU5xpKm6x6w]
x-ms-publictraffictype: Email
x-incomingheadercount: 45
x-eopattributedmessage: 0
x-ms-office365-filtering-correlation-id: b3d1a443-a0a3-45c9-a63a-08d7fd2635ab
x-ms-traffictypediagnostic: SN1NAM04HT019:
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info:
 lrnC4s40XXftg6QwFimdkDW/sfQdZ9d3LXZB6v9TW5yPdnOw5viSGGaekx4wWByJ5L6XmPLLrW4GXYiJIwJmsj4NZagPuJQp3y/UFBFjw14i9/yp5IhEpAM3yqwoPokxmR/6elR/JPPBKuY56iSW8vISa4Dod5VQO4iyBLJ+6AW3ZnWW4Abd4m7/5OhtX/B9wXEoFRXtKwOnffAUo4BlQY37tg21JUYwWPoLKUN3M2CSmMvsDQDg6gBQnhd5JrP3
x-forefront-antispam-report:
 CIP:255.255.255.255;CTRY:;LANG:en;SCL:0;SRV:;IPV:NLI;SFV:NSPM;H:DM6PR07MB6618.namprd07.prod.outlook.com;PTR:;CAT:NONE;SFTY:;SFS:;DIR:OUT;SFP:1901;
x-ms-exchange-antispam-messagedata:
 jjysKtXrRiWHGmnu9QLt3sm46ePtQfqbqCvaSO8d9dkG+LiXBDWrthBrOijyVj65Z4oW+8nUFE/C8D+CPirG/MGZkbnLdkSBGhJEIU+PcNwwhtGXIG8ZC52V6s1dSLlJjJhTcV0dvahGntaRXh+k64GavP5J7gv7yrCHxOKNfu+HnU8ituTgvMF7Bk822C+ZMfqvZQcsTDloaEHFVKN/Rg==
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: hotmail.com
X-MS-Exchange-CrossTenant-RMS-PersistedConsumerOrg: 00000000-0000-0000-0000-000000000000
X-MS-Exchange-CrossTenant-Network-Message-Id: b3d1a443-a0a3-45c9-a63a-08d7fd2635ab
X-MS-Exchange-CrossTenant-rms-persistedconsumerorg: 00000000-0000-0000-0000-000000000000
X-MS-Exchange-CrossTenant-originalarrivaltime: 21 May 2020 01:28:04.6481
 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Internet
X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa
X-MS-Exchange-Transport-CrossTenantHeadersStamped: SN1NAM04HT019
Subject: Re: [PHP-DEV] Draft RFC callable types + callable type/function
 autoloading
From: tysonandre775@hotmail.com (tyson andre)

Hi Dan Ackroyd,=0A=
=0A=
> Function + callable type autoloading=0A=
> https://github.com/Danack/FunctionTypes/blob/master/2_autoloading_part_2.=
md=0A=
=0A=
I'd be happy to see function autoloading support in php overall.=0A=
It'd help in avoiding loading unnecessary polyfills, or in large codebases =
with many global functions that are only occasionally used.=0A=
=0A=
Autoloading functions involves a lot of tradeoffs due to design choices in =
PHP.=0A=
I've seen a lot of different opinions - It might be worth setting up a stra=
w poll for whether people would be interested in the change, unless you exp=
ect the php 8 implementation to be easy.=0A=
(though straw polls have much lower response rates than RFCs)=0A=
=0A=
- Functions can be added to a namespace after they get added to the global =
scope.=0A=
- A lot of namespaced php code refers to functions ambiguously=0A=
(`namespace Foo; echo strlen($x);` can either refer to `strlen()` or `Foo\s=
trlen`).=0A=
  What were your plans for handling ambiguous calls?=0A=
  I was in favor of checking if either existed (current behavior) before au=
toloading `Foo\strlen`, then before autoloading `strlen`, to keep performan=
ce acceptable.=0A=
  Others preferred various alternate approaches to autoloading.=0A=
  I don't think there was ever a straw poll to measure how common other opi=
nions were,=0A=
  or if people would accept a given approach despite having a preference fo=
r something else.=0A=
=0A=
The alternatives I can imagine/remember from previous RFC discussions, *non=
e of which I hold* (https://wiki.php.net/rfc/use_global_elements#deprecate_=
the_fallback_to_the_root_namespace_instead and below had somewhat related d=
iscussion as an attempt to reduce ambiguity):=0A=
=0A=
- The exact way to deal with ambiguity when autoloading, e.g. "autoload Foo=
\strlen() every single time strlen() is called" (I object because that woul=
d harm performance significantly)=0A=
- You should make calling static methods easier (doesn't help with a lot of=
 internal functionality like strlen() or polyfills for PECL functions are g=
lobal functions)=0A=
=0A=
Other thoughts:=0A=
=0A=
- Maybe it would be useful/practical to initially *just* support autoloadin=
g functions when they're passed to function_exists($name, autoload: true) o=
r autoload_function($name).=0A=
  I don't remember if that approach was suggested before.=0A=
  Then again, I'd personally want something more powerful than that due to =
the inconvenience, and I imagine most people would.=0A=
=0A=
Thanks,=0A=
- Tyson=