Re: High performance function autoloading

Hello, "Disabling function mocking is good", in my life I read many idioties; this one gets the "Palme d'Or"; This majesty; crowned Emperor. On Mon, May 20, 2019 at 11:45 AM Marco Pivetta <ocramius@gmail.com> wrote: > 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. >