Re: [PHP-DEV] [RFC] [VOTE] Function Autoloading (mark 5)
[email protected] ("Paul M. Jones") Fri, 31 Jul 2026 11:03:37 -0500
| Newsgroups | php.internals |
|---|---|
| Message-ID | <[email protected]> |
Hi, > On Jul 31, 2026, at 10:52, Tim D=C3=BCsterhus <[email protected]> = wrote: >=20 > Hi >=20 > On 2026-07-31 15:09, Paul M. Jones wrote: >>> In fact the start of the vote is in violation of our policy, since = there was no =E2=80=9Cintent to vote=E2=80=9D message in the last 7 = days. >> Ah so -- my apologies. I'll pull the vote and wait for ... looks like = ~6 weeks? >=20 > According to policy you could cancel the vote now, which results in a = 2-week cooldown, which means you could theoretically re-open in the = middle of August (after another =E2=80=9CIntent to Vote=E2=80=9D). >=20 > However given the preliminary voting results and under the assumption = that folks didn't just vote against due to the policy violation, it is = likely not useful to reopen the vote without making further changes - or = without the circumstances changing (specifically your =E2=80=9CStrict = Namespace Resolution=E2=80=9D RFC getting a decision). In any case, = there will be plenty of time until PHP 8.7. >=20 > Without giving it detailed thought, I believe =E2=80=9CNamespaced = function, Autoload namespaced function, Global fallback=E2=80=9D (i.e. = swap steps 2 and 3) would result in much more predictable semantics = already - the global fallback would work just as before, it just = wouldn't have autoloading support. It's quite possible I'm changing my = mind on that as well when I think more about it, but I wanted to provide = some food for thought as to how the RFC could possibly be adjusted to = make it better. Sure, no hurry on my part. Can come back to it after 8.6 is fully out = the door. I have edited the RFC to set the vote to "closed" -- let me know if some = other approach is preferred. Thanks! -- pmj