Re: Guidelines for RFC post feature-freeze
| From: | Derick Rethans | Date: | Tue, 24 Aug 2021 19:09:05 +0000 |
| Subject: | Re: Guidelines for RFC post feature-freeze | ||
| References: | 1 2 3 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-115794@lists.php.net to get a copy of this message | ||
On 24 August 2021 19:53:57 BST, Deleu <deleugyn@gmail.com> wrote:
>On Tue, Aug 24, 2021, 19:28 Derick Rethans <derick@php.net> wrote:
>
>> On Mon, 23 Aug 2021, Deleu wrote:
>>
>> > We recently had the Nullable Intersection Types RFC process in an
>> > unconventional way starting a new RFC post feature freeze. If memory
>> > serves me right, another similar incident happened with the Attributes
>> > RFC which had a syntax that could not be implemented without a
>> > secondary RFC [1] and went through a secondary RFC which proposed a
>> > different syntax [2].
>>
>> I find this comparison disingenuous.
>>
>
>I want to state that I had no intention to compare the RFCs or even bring
>their merits into discussion. What I intended to show is that we have 8.0
>which had an RFC that would classify as Refinement RFC and 8.1 again having
>another RFC that also classifies under the same category.
That's where I disagree already. The nullable intersections RFC isn't a refinement,
it's a new feature.
cheers
Derick