Re: High performance function autoloading
| From: | Marco Pivetta | Date: | Mon, 20 May 2019 18:45:16 +0000 |
| Subject: | Re: High performance function autoloading | ||
| References: | 1 2 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-105761@lists.php.net to get a copy of this message | ||
On Mon, 20 May 2019, 20:01 Gabriel O, <gadelat@gmail.com> wrote:
>
> On 20 May 2019 7:17:58 PM Theodore Brown <theodorejb@outlook.com> wrote:
>
> > Every time function autoloading been brought up in the past, there
> > have been concerns about performance issues when calling a global
> > function from inside a namespace. E.g. calling
strlen in a
> > loop
> > would become far slower if every call has to trigger the autoloader.
>
> This trick for perf improvement is overblown. It's misconception that it
> does provide speed advantage for most functions and reasons behind it. It
> does so only for those implemented as opcodes. People started to abuse it
> by importing ALL functions. Such overzealous approach completely prevents
> useful things like function mocking.
>
Disabling function mocking is good ©️
It was a terrible practice in first place, and it is usually done for
impure functions that should be wrapped in integration-tested adapters.