> The problem with stop-gap measures is they become entrenched, and the proper solution doesn't get implemented
This would be my general point of view - unfortunately, functions are essentially useless at present, in a world with Composer, unless you're willing to preload all functions from all packages up-front. The only suggested solutions I've heard for the name resolution issue with function autoloading frankly are all horrible - much worse than this simple alternative. Add to that the fact that likely 90% of all functions in the wild (at least in Composer packages) are currently implemented as public static functions, and in my opinion, this is starting to sound less like a stop-gap and more like a simple solution to a problem we've been solving with a stop-gap for, oh, 10 years or so... On Jan 26, 2017 10:05 AM, "Andrea Faulds" <a...@ajf.me> wrote: > Hi, > > Rasmus Schultz wrote: > >> Since the autoloading functions proposal is stalled, how about allowing >> for >> import of static functions instead? >> > > The problem with stop-gap measures is they become entrenched, and the > proper solution doesn't get implemented. But we may be at the risk of the > latter anyway. > > -- > Andrea Faulds > https://ajf.me/ > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > >
