Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:128210
Precedence: bulk
MIME-Version: 1.0 (Mimestream 1.7.1)
References: <CALaXqqRu0DBHpTNavte9FcaXQDf8PZ8W=4QR=dhDGajQ5devaA@mail.gmail.com>
In-Reply-To: <CALaXqqRu0DBHpTNavte9FcaXQDf8PZ8W=4QR=dhDGajQ5devaA@mail.gmail.com>
Date: Thu, 24 Jul 2025 06:37:34 -0700
Message-ID: <CAEPJdu=OdJdJMj2bQ2vZOzHckOfAtSKtUoKYqZgfWRX9kaDWVg@mail.gmail.com>
Subject: Re: [PHP-DEV] [VOTE] RFC: #[\DelayedTargetValidation] attribute
To: Daniel Scherzer <daniel.e.scherzer@gmail.com>
Cc: php internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000b803bd063aaced17"
From: kontakt@beberlei.de (=?UTF-8?Q?Benjamin_Au=C3=9Fenhofer?=)

--000000000000b803bd063aaced17
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Am 17.07.2025, 18:21:10 schrieb Daniel Scherzer <daniel.e.scherzer@gmail.co=
m
>:

> Hi internals,
>
> Voting is now open for this RFC.
>
> * RFC: https://wiki.php.net/rfc/delayedtargetvalidation_attribute
> * Discussion thread: https://externals.io/message/127702
>
> Voting will end 2025-07-31 at end-of-day UTC.
>
> -Daniel
>

As one of the original attributes RFC authors, I have voted yes on this and
hope it passes.

its unfortunate that we need to do this, because its a bit of a hacky
solution, but its entirely the vault of the original implementation, we
didn't think of this.

And that we didn=E2=80=99t think of it during the Deprecated RFC as well an=
d
already set the target validation to the max and just not do anyhting with
the attribute.

I think a better fix could be to delay target validation automatically to
the point when the Engine consumes an attribute, but that would change the
original behavior and not sure if that would get a majority, so an opt
<http://opt.in>-in approach is the least bad solution to fix this
shortcoming. Another solution, since this will work only with new
attributes, would be more informal: that we set target=3Dall for compiler
attributes from now on, at least for attributes where we think they could
expand in targets in the future.

greetings
Benjamin

--000000000000b803bd063aaced17
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<html><body><div dir=3D"ltr">
    <br>
</div>
<br>
<div class=3D"gmail_quote">
    <div dir=3D"ltr" class=3D"gmail_attr">Am 17.07.2025, 18:21:10 schrieb D=
aniel Scherzer &lt;<a href=3D"mailto:daniel.e.scherzer@gmail.com">daniel.e.=
scherzer@gmail.com</a>&gt;:<br></div>
    <blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;bor=
der-left:1px solid rgb(204,204,204);padding-left:1ex" type=3D"cite">
        <div dir=3D"ltr">Hi internals,<br><br>Voting is now open for this R=
FC.<br><br>* RFC:=C2=A0<a href=3D"https://wiki.php.net/rfc/delayedtargetval=
idation_attribute">https://wiki.php.net/rfc/delayedtargetvalidation_attribu=
te</a><br>* Discussion thread:=C2=A0<a href=3D"https://externals.io/message=
/127702">https://externals.io/message/127702</a><div><br>Voting will end 20=
25-07-31 at end-of-day UTC.</div><div><br></div><div>-Daniel</div></div>

    </blockquote><br>
</div><div class=3D"gmail_quote" dir=3D"ltr">As one of the original attribu=
tes RFC authors, I have voted yes on this and hope it passes.</div><div cla=
ss=3D"gmail_quote" dir=3D"ltr"><br></div><div class=3D"gmail_quote" dir=3D"=
ltr">its unfortunate that we need to do this, because its a bit of a hacky =
solution, but its entirely the vault of the original implementation, we did=
n&#39;t think of this.=C2=A0</div><div class=3D"gmail_quote" dir=3D"ltr"><b=
r></div><div class=3D"gmail_quote" dir=3D"ltr">And that we didn=E2=80=99t t=
hink of it during the Deprecated RFC as well and already set the target val=
idation to the max and just not do anyhting with the attribute.=C2=A0</div>=
<div class=3D"gmail_quote" dir=3D"ltr"><br></div><div class=3D"gmail_quote"=
 dir=3D"ltr">I think a better fix could be to delay target validation autom=
atically to the point when the Engine consumes an attribute, but that would=
 change the original behavior and not sure if that would get a majority, so=
 an <a href=3D"http://opt.in">opt</a>-in approach is the least bad solution=
 to fix this shortcoming. Another solution, since this will work only with =
new attributes, would be more informal: that we set target=3Dall for compil=
er attributes from now on, at least for attributes where we think they coul=
d expand in targets in the future.</div><div class=3D"gmail_quote" dir=3D"l=
tr"><br></div><div class=3D"gmail_quote" dir=3D"ltr">greetings</div><div cl=
ass=3D"gmail_quote" dir=3D"ltr">Benjamin</div><div class=3D"gmail_quote" di=
r=3D"ltr"><br></div></body></html>

--000000000000b803bd063aaced17--