Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:103335
MIME-Version: 1.0
References: <BY1PR02MB12602A77B8FA30A9D5443DD5BFF90@BY1PR02MB1260.namprd02.prod.outlook.com>
In-Reply-To: <BY1PR02MB12602A77B8FA30A9D5443DD5BFF90@BY1PR02MB1260.namprd02.prod.outlook.com>
Date: Fri, 19 Oct 2018 11:56:23 +0200
Message-ID: <CA+GmM=wj076+AG00awREibNSBAjFUOeO5s-eK-7aH2-kZ+uhUg@mail.gmail.com>
To: Dmitry Stogov <dmitry@zend.com>
Cc: PHP Developers Mailing List <internals@lists.php.net>
Content-Type: text/plain; charset="UTF-8"
Subject: Re: [PHP-DEV] [RFC] Preloading
From: j.boggiano@seld.be (Jordi Boggiano)

On Fri, 19 Oct 2018 at 10:18, Dmitry Stogov <dmitry@zend.com> wrote:
> I would like to start discussion on a Preloadng RFC https://wiki.php.net/rfc/preload

This sounds great!

If I understand correctly, this could also be included in Composer as
a new autoload type "preload" (which would be an array of files to
preload in a given package), so that Composer would generate
vendor/composer/preload.php as a list of includes to all the files in
every installed package that asked for preloading. Sounds like a
relatively easy addition that would let any library define their own
symbols. Obviously users can then choose to preload that file or not.

JIT-ing the sum of all preloaded classes/functions as once vs
function-level JIT also sounds like a very exciting prospect!

Best,
Jordi