Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:128084
Precedence: bulk
MIME-Version: 1.0
Date: Wed, 16 Jul 2025 15:53:06 +0200
To: Derick Rethans <derick@php.net>
Cc: Dmitry Derepko <xepozzd@gmail.com>, PHP internals
 <internals@lists.php.net>
Subject: Re: [PHP-DEV] [RFC] [Discussion] CHIPS
In-Reply-To: <35861960-bf43-1396-5cfa-3bf18ea1ca84@php.net>
References: <CANTuiHsW99Ny-Cx1+kyU0+Q4bimnGWZe+stWd0wvSSfO=zwvgw@mail.gmail.com>
 <35861960-bf43-1396-5cfa-3bf18ea1ca84@php.net>
Message-ID: <d499cff29f5bcec42a37046c171f6eb2@bastelstu.be>
Content-Type: text/plain; charset=UTF-8;
 format=flowed
Content-Transfer-Encoding: 8bit
From: tim@bastelstu.be (=?UTF-8?Q?Tim_D=C3=BCsterhus?=)

Hi

>> As Niels noted, today is the day when in 4 weeks there will be code
>> freeze, so let's try to fit into the lines and deliver the value to
>> PHP 8.5.
> 
> I'm not so keen on trying to rush things before meeting a deadline, but
> I think that this addition seems entirely reasonable.

I agree on both of these points. The RFC appears well-researched 
(including the support for sessions, which I would likely not have 
thought of myself) and has a very straight forward implementation, since 
it's just extending an existing API based on an external standard, 
making it reasonably risk-less.

As to the RFC text itself, I like how carefully the “RFC Impact” section 
of the updated RFC template [1] has been filled in. I don't have any 
other remarks, except LGTM :-)

Best regards
Tim Düsterhus

[1] https://externals.io/message/127834