Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:130740
Precedence: list
MIME-Version: 1.0
References: <CABVsipicHroAcWJSEpjwM4+y6p-6axV-6tO__MejThESFVCP3A@mail.gmail.com>
 <CABdc3WrsYzNd=s5LYkpqphVr_PWVEOyDCcZcC9QkzhKUU7r2ow@mail.gmail.com>
 <CABVsipgfS2j49iBm38X8g1N1RdVZfHudaBqBrdNLfTMpUZfC2w@mail.gmail.com>
 <f0a77882-44e2-4cd9-be14-eca9163194ca@app.fastmail.com> <CABVsipjQiay5NK36Rwtwk6tDi0mRwa+Wv4oSz17qR_vwresYfw@mail.gmail.com>
 <19d58a46b50222b75da4e40e417efd05@bastelstu.be> <CABVsiph+=CeAkAL6XwzD57qDPt=24r8sh4HV32BOPmRFXfTqSw@mail.gmail.com>
 <4f684a4fbad3a7ddb797e24e3c1a882a@bastelstu.be> <8dca7d45-fce4-4d6a-ac56-956046ef20a6@app.fastmail.com>
 <df6ddecef3b8f61583977721dcf9976f@bastelstu.be> <CABVsipgWoX1bNa69wUi0AmGK4-62WkNsaWj965QT4ocyz9_wCg@mail.gmail.com>
 <186bc870ee3e713cefab18a6d45d4dcb@bastelstu.be>
In-Reply-To: <186bc870ee3e713cefab18a6d45d4dcb@bastelstu.be>
Date: Sat, 2 May 2026 09:28:14 +0200
Message-ID: <CABVsipiutKgKnQpkRoRd3T_1035g_WCiDdvoYL6rW357_6Rtdg@mail.gmail.com>
Subject: Re: [PHP-DEV] [RFC] [Discussion] array_get and array_has functions
To: php internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000af10c80650d0a4d2"
From: barel.barelon@gmail.com (Barel)

--000000000000af10c80650d0a4d2
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Thu, 30 Apr 2026 at 09:34, Tim D=C3=BCsterhus <tim@bastelstu.be> wrote:

> Hi
>
> Am 2026-04-25 21:37, schrieb Barel:
> > Many thanks for your comments regarding the RFC, I have updated it.
>
> I'm seeing you adjusted the text to mention =E2=80=9CIf any segment is no=
t a
> string or integer: throw a TypeError, even if that segment would not be
> reached=E2=80=9D. This is however not reflected in the example implementa=
tion.
>

Thanks for pointing this out. This has been updated in the RFC

Carlos

--000000000000af10c80650d0a4d2
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">On Thu, 30 Apr 2026 at 09:34, Tim D=C3=BC=
sterhus &lt;<a href=3D"mailto:tim@bastelstu.be">tim@bastelstu.be</a>&gt; wr=
ote:</div><div class=3D"gmail_quote gmail_quote_container"><blockquote clas=
s=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid r=
gb(204,204,204);padding-left:1ex">Hi<br>
<br>
Am 2026-04-25 21:37, schrieb Barel:<br>
&gt; Many thanks for your comments regarding the RFC, I have updated it.<br=
>
<br>
I&#39;m seeing you adjusted the text to mention =E2=80=9CIf any segment is =
not a <br>
string or integer: throw a TypeError, even if that segment would not be <br=
>
reached=E2=80=9D. This is however not reflected in the example implementati=
on.<br></blockquote><div><br></div><div>Thanks for pointing this out. This =
has been updated in the RFC</div><div><br></div><div>Carlos=C2=A0</div></di=
v></div>

--000000000000af10c80650d0a4d2--