Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:127096
Precedence: bulk
MIME-Version: 1.0
References: <CAPTD5yHhpcJJDNWMCpQSrkGyY5+YtgKUy1OKYv5t03KyzoAXbA@mail.gmail.com>
 <CAEKnhAFdwYV1D+Dt+LzwVdzPAaa904ORnMBe0piN0G86g7v-iA@mail.gmail.com>
In-Reply-To: <CAEKnhAFdwYV1D+Dt+LzwVdzPAaa904ORnMBe0piN0G86g7v-iA@mail.gmail.com>
Date: Fri, 11 Apr 2025 12:40:29 +0200
Message-ID: <CAEKnhAFGTGHnWLh2Tvd1Rxbz54Y=zfQf9P2nZQULXoExFraDRQ@mail.gmail.com>
Subject: Re: [PHP-DEV] Consensus on argument validation for built-in functions
To: Jorg Sowa <jorg.sowa@gmail.com>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="00000000000076d33106327e552c"
From: bukka@php.net (Jakub Zelenka)

--00000000000076d33106327e552c
Content-Type: text/plain; charset="UTF-8"

>
>
> This thread clearly shows that there is no consensus so I think the only
> way forward would be to create a policy RFC to make decision about this
> approach. Until then no PR introducing exception, deprecation or just plain
> warning for this sort of things should be merged.
>
>
In terms of RFC, in this case we need some decision so it might make sense
to do something like primary vote just to be an approval to make any
changes (e.g. "Add clarification to policy about argument validation") and
then just add secondary vote as a choice between deprecation or straight
going to value error.

--00000000000076d33106327e552c
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_quote gmail_quote_container"><blockquo=
te class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px =
solid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr"><div class=3D"gma=
il_quote"><div><br></div><div>This thread clearly shows that there is no co=
nsensus so I think the only way forward would be to create a policy RFC to =
make decision about this approach. Until then no PR introducing exception, =
deprecation or just plain warning for this sort of things should be merged.=
</div><div><br></div></div></div></blockquote><div><br></div><div>In terms =
of RFC, in this case we need some decision so it might make sense to do som=
ething like primary vote just to be an approval to make any changes (e.g. &=
quot;Add clarification to policy about argument validation&quot;) and then =
just add secondary vote as a choice between deprecation or straight going t=
o value error.=C2=A0=C2=A0</div></div></div>

--00000000000076d33106327e552c--