As I previously wrote in the old Thread, ...
I would like to say that we should keep the release process as it is,
until a true, real, use case shows up.
Whoever participated in the threads is already aware about the so many
possibilities, and adjustments to the release/work process , that have
t
> On 12 Oct 2022, at 11:06, Jordan LeDoux wrote:
>
> 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 i
On Tue, Oct 11, 2022 at 6:44 PM David Rodrigues
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 (whic
>From what I understand, your concern is "what if we need to change the
direction of something already decided"? For example, initially it was
decided and very well accepted private(set), but after a while the idea was
revised and it was decided that private:set would be better instead.
In this ca
On Tue, Oct 11, 2022, at 8:43 PM, David Rodrigues wrote:
> Nice example!
>
>> You're saying that "public private(set)" would become available in 8.2.1
> (the late-December release of 8.2), but only in files that have
> "declare(asymmetric_visibility=1);" at the top.
>
> Yes. In that case, I should
Nice example!
> You're saying that "public private(set)" would become available in 8.2.1
(the late-December release of 8.2), but only in files that have
"declare(asymmetric_visibility=1);" at the top.
Yes. In that case, I should suggest declare(preview_asymmetric_visibility =
1), just to make cle
On Tue, Oct 11, 2022, at 3:25 PM, David Rodrigues wrote:
> In order to try to organize a little better the original purpose of the
> discussion I started, I decided to "rename" this subject to something
> closer to the purpose. From "experimental features" to "feature preview".
>
> Original thread:
In order to try to organize a little better the original purpose of the
discussion I started, I decided to "rename" this subject to something
closer to the purpose. From "experimental features" to "feature preview".
Original thread: https://marc.info/?l=php-internals&m=166491585711553
These are m
