On Thu, Sep 3, 2020 at 8:23 PM Levi Morrison <levi.morri...@datadoghq.com> wrote:
> > 3. Better visibility from the JIT (not having to cross > userspace/internals > > border is good) > > This is a good point _in theory_, but to me this is just indicative > that we need to be able to bundle built-in functions for php-src. Now > that we have preloading, I wonder how far off we are from achieving > this in some form. > Mostly an orthogonal topic, though I do agree that as the JIT matures we may find we particularly want to move in this direction. It certainly makes sense to build in the capability sooner rather than later. Thinking about ways to negate the other two issues I brought up... 1. Forward-compat; We could produce a smaller distributable package containing just the script builtin implementations for use on older versions. Use some mechanism to mark which versions they're introduced in and selectively pull them out or something. Or maybe do that external to the project (anyone could pull these definitions out and package them for composer). 2. Bugfixing; I wonder if it makes sense to allow preload files to override builtin functions. Then a fix in git could be pulled in before a new release is ever minted without the need for rebuilds. Similarly, hooks could be added to any function to customize them for private installs. Again, no rebuilds, no special skills required. Just thinking out loud. -Sara
