Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:126456
Feedback-ID: ifab94697:Fastmail
Precedence: bulk
MIME-Version: 1.0
Date: Tue, 18 Feb 2025 20:37:09 +0100
To: internals@lists.php.net
Message-ID: <c3c7824a-3608-4fd2-b092-d82d572b502c@app.fastmail.com>
In-Reply-To: <dc2a4e4b-ac0c-4ecd-9146-8cf6463cf57a@bastelstu.be>
References: <04b901db8225$788d5250$69a7f6f0$@glaive.pro>
 <e4ee0d92-f7c1-46b5-935a-50d5cfc91b41@app.fastmail.com>
 <dc2a4e4b-ac0c-4ecd-9146-8cf6463cf57a@bastelstu.be>
Subject: Re: New RFC discussions (was: Re: [PHP-DEV] Fully overridable factory methods)
Content-Type: multipart/alternative;
 boundary=dd0a6d0cf6b246e5b264ad8982e748f0
From: rob@bottled.codes ("Rob Landers")

--dd0a6d0cf6b246e5b264ad8982e748f0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

On Tue, Feb 18, 2025, at 20:24, Tim D=C3=BCsterhus wrote:
> Hi
>=20
> On 2/18/25 18:31, Rob Landers wrote:
> > You may be interested in a super-draft RFC that I=E2=80=99ll propose=
 in the next few days=E2=80=A6
>=20
> May I kindly request some breathing room with regard to new RFC=20
> discussions so that folks are able to give each RFC the proper=20
> attention. The list currently is super active. We have:
>=20
> - 2 Votes in progress (FCC in constexpr, aviz for static)
> - 6 discussions with RFC written (NoDiscard, get_error_handler, URI,=20
> Compression, Optional Interfaces, Pipe)
> - and several non-RFC or pre-RFC discussions (Async, Constructor=20
> Overloading, Not Null Assertions, =E2=80=A6)
>=20
> This is already approximately 3 RFC discussions too many. Perhaps wait=20
> until Mid-March or so? I expect at least some of the currently discuss=
ed=20
> RFCs to be in voting by then.
>=20
> Best regards
> Tim D=C3=BCsterhus
>=20

Hi Tim,

I assume you are speaking to me, personally?

This will be opened as a draft before proposing it to the list, which wi=
ll indeed (probably) be around mid-March, pending solicited feedback, so=
 no worries. I also have a couple drafts/in-discussion to close that thi=
s new RFC will supersede.

=E2=80=94 Rob
--dd0a6d0cf6b246e5b264ad8982e748f0
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE html><html><head><title></title><style type=3D"text/css">p.Mso=
Normal,p.MsoNoSpacing{margin:0}</style></head><body><div>On Tue, Feb 18,=
 2025, at 20:24, Tim D=C3=BCsterhus wrote:<br></div><blockquote type=3D"=
cite" id=3D"qt" style=3D""><div>Hi<br></div><div><br></div><div>On 2/18/=
25 18:31, Rob Landers wrote:<br></div><div>&gt; You may be interested in=
 a super-draft RFC that I=E2=80=99ll propose in the next few days=E2=80=A6=
<br></div><div><br></div><div>May I kindly request some breathing room w=
ith regard to new RFC&nbsp;<br></div><div>discussions so that folks are =
able to give each RFC the proper&nbsp;<br></div><div>attention. The list=
 currently is super active. We have:<br></div><div><br></div><div>- 2 Vo=
tes in progress (FCC in constexpr, aviz for static)<br></div><div>- 6 di=
scussions with RFC written (NoDiscard, get_error_handler, URI,&nbsp;<br>=
</div><div>Compression, Optional Interfaces, Pipe)<br></div><div>- and s=
everal non-RFC or pre-RFC discussions (Async, Constructor&nbsp;<br></div=
><div>Overloading, Not Null Assertions, =E2=80=A6)<br></div><div><br></d=
iv><div>This is already approximately 3 RFC discussions too many. Perhap=
s wait&nbsp;<br></div><div>until Mid-March or so? I expect at least some=
 of the currently discussed&nbsp;<br></div><div>RFCs to be in voting by =
then.<br></div><div><br></div><div>Best regards<br></div><div>Tim D=C3=BC=
sterhus<br></div><div><br></div></blockquote><div><br></div><div>Hi Tim,=
</div><div><br></div><div>I assume you are speaking to me, personally?</=
div><div><br></div><div>This will be opened as a draft before proposing =
it to the list, which will indeed (probably) be around mid-March, pendin=
g solicited feedback, so no worries. I also have a couple drafts/in-disc=
ussion to close that this new RFC will supersede.<br></div><div><br></di=
v><div id=3D"sig121229152">=E2=80=94 Rob<br></div></body></html>
--dd0a6d0cf6b246e5b264ad8982e748f0--