Re: Asymmetric Property Write Performance
| From: | Calvin Buckley | Date: | Tue, 14 Jul 2026 17:32:49 +0000 |
| Subject: | Re: Asymmetric Property Write Performance | ||
| References: | 1 2 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-131920@lists.php.net to get a copy of this message | ||
On Jul 14, 2026, at 2:11 PM, Holly Schilling <holly.a.schilling@outlook.com> wrote:
>
>> correct me if I'm wrong, but I don't see why that would be a RFC. (Small)
>> internal changes with no change in userland don't go through the RFC process and are handled on
>> GitHub instead. This should also target the supported version (8.4) instead of master.
>
> Honestly, I don’t know the norms for this kind of thing. This is a small change, but it
> involves an ABI breaking change. That was why I thought it should target a new release chain (8.6)
> rather than applying it to 8.4. If anyone wants to help me steward this out of being a draft, I
> would welcome the advice.
>
> Holly
>
For internal API breaking changes, it should definitely target master. Usually for stuff smaller
changes in that purview, you shouldn't need an RFC unless requested.