Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:118805
MIME-Version: 1.0
References: <CAEsg9X0YvRHHKCfFfkR3uYmzwpFps54GvmD7dCcJyXv3nwio-g@mail.gmail.com>
 <a187de08-9488-4407-9255-5bd57ee3daf6@app.fastmail.com> <CAEsg9X2KMAaZnSEqg+36-zZ-p49awoVeuRUnMm4PYJSGYZ--KA@mail.gmail.com>
In-Reply-To: <CAEsg9X2KMAaZnSEqg+36-zZ-p49awoVeuRUnMm4PYJSGYZ--KA@mail.gmail.com>
Date: Wed, 12 Oct 2022 01:06:51 -0700
Message-ID: <CAMrTa2EfY2Zxxuawm-oNAWicq7VP7L6G-EgcfpVAFoDOKGjFQg@mail.gmail.com>
To: David Rodrigues <david.proweb@gmail.com>
Cc: Larry Garfield <larry@garfieldtech.com>, php internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000c08e9905ead1e05f"
Subject: Re: [PHP-DEV] Feature preview (formely was: experimental features)
From: jordan.ledoux@gmail.com (Jordan LeDoux)

--000000000000c08e9905ead1e05f
Content-Type: text/plain; charset="UTF-8"

On Tue, Oct 11, 2022 at 6:44 PM David Rodrigues <david.proweb@gmail.com>
wrote:

>
> Partially. As the usage definition has not yet been decided between
> private(set) vs. private:set, so this feature is not ready for preview.
> Unless the idea of allowing the two syntaxes to co-exist in this feature is
> acceptable (which I personally think is a bad idea).
>
>
If a "preview" doesn't allow us to make breaking changes, then what exactly
is the point? I don't see any benefit at all to this without that.

If the "preview" is *actually* just "put out an RFC in the next patch
release as soon as it's merged to master", which is what it seems you're
saying (as that seems like all that's left with all the things you said we
can't do in a preview), then that seems dubious, prone to instability in
the engine outside of the preview features, and a total breakage of the
release cycle and RM process that is currently in place.

Jordan

--000000000000c08e9905ead1e05f--