Re: Guidelines for RFC post feature-freeze
| From: | Derick Rethans | Date: | Tue, 24 Aug 2021 17:28:51 +0000 |
| Subject: | Re: Guidelines for RFC post feature-freeze | ||
| References: | 1 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-115788@lists.php.net to get a copy of this message | ||
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. The changes to the Attribute Syntax
wasn't a new feature, and started well before feature freeze. and only
just missed it, and some of that time wasted was arguably due to not
being able to count.
The RFC on nullable intersections is a NEW feature, and was started a
week after feature freeze had already happened. It was *not* a mistake
as the feature was specifically introduced as "pure intersection types",
as outlined in the RFC, and re-articulated by the author in an interview
(https://phpinternals.news/88#transcript)
cheers,
Derick
--
PHP 7.4 Release Manager
Host of PHP Internals News: https://phpinternals.news
Like Xdebug? Consider supporting me: https://xdebug.org/support
https://derickrethans.nl | https://xdebug.org | https://dram.io
twitter: @derickr and @xdebug