Hi Mark, I'm a fan of adding an easy and performant way to implement classmap-based autolading, but weary of adding yet another way to autoload. If it would be possible to do so without negating the performance improvements, I'd suggest having this work in conjunction with the existing spl_autoload_register rather than introducing two different ways to specify autoloaders. I.e., usage would look like:
spl_autoload_register(autoload_classmap($mapping)); Cheers, --Matthew On Mon, Apr 5, 2021 at 3:05 PM Mark Randall <marand...@php.net> wrote: > On 15/03/2021 17:41, Mark Randall wrote: > > I would like to propose the addition of a new mechanism of autoloading > > classes - a classmap that will be consulted prior to checking the > > spl_autoload_register'd callbacks. > > > > https://wiki.php.net/rfc/autoload_classmap > > Does anyone else have any more feedback on this? If not I plan on > opening voting in a couple of weeks or so. > > The tl;dr: > > * Autoloading is one of the routines called most frequently in any request. > > * It's a very minor boost in autoloading performance, around 5% vs > invoking a userland function. This will easily be swamped by any IO and > invalidated entirely by preloading. > > * I expect 99.9999% of users will never know it exists, and it will > instead just be an option for tools like composer that will provide a > small transparent boost. > > * It provides a very minor benefit to debugging as you get to skip over > the autoloading frames which so very often come up during a request. > > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: https://www.php.net/unsub.php > >
