Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:111593
Content-Type: text/plain;
	charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.1\))
In-Reply-To: <CALKiJKoaPA-8-Eb1ceoDvp6G_q-uVSJCG3tpbtj=VfXvW-sW=A@mail.gmail.com>
Date: Mon, 17 Aug 2020 12:30:10 -0500
Cc: Internals <internals@lists.php.net>
Content-Transfer-Encoding: quoted-printable
Message-ID: <419877AD-FCC8-470C-8296-6A5FD975584D@joshbruce.dev>
References: <C30D6E89-9521-4106-B55A-590CCD3F4986@joshbruce.dev>
 <747c6d622bbadebf32a8b7dec541c333eeb8776a6ab7ff0784a0b75c8895a646@mahalux.com>
 <CALKiJKoaPA-8-Eb1ceoDvp6G_q-uVSJCG3tpbtj=VfXvW-sW=A@mail.gmail.com>
To: Rowan Tommins <rowan.collins@gmail.com>
Subject: Re: [PHP-DEV] [Concept] Don't cast keys in array to int
From: josh@joshbruce.dev (Josh Bruce)

Thanks Rowan. I can appreciate that rationale.

Also let=E2=80=99s me in on why we might want to have an indexed array =
that is not necessarily sequential - but are integers.

Thanks again.

Cheers,
Josh

> On Aug 17, 2020, at 4:17 AM, Rowan Tommins <rowan.collins@gmail.com> =
wrote:
>=20
> On Mon, 17 Aug 2020 at 05:19, Michael Vo=C5=99=C3=AD=C5=A1ek - =C4=8CVUT=
 FEL <
> vorismi3@fel.cvut.cz> wrote:
>=20
>> This seems almost as a bug, strict types should apply also for array =
key
>> which is currently not the case.
>>=20
>> https://3v4l.org/epv5s
>=20
>=20
>=20
> No, it really shouldn't. In hindsight, "strict_types" was a bad name =
for
> that directive; it is not a catch-all "make the type system stricter" =
flag,
> it changes one specific piece of logic: when passing a scalar value to =
a
> function parameter annotated with a different scalar type, should the =
value
> be automatically cast, or require a manual cast. There is no function =
call
> in that code example, so the directive has no effect.
>=20
>=20
> The reason PHP treats $foo[42] as referring to the same element as
> $foo['42'] is to support this straight-forwardly useful code:
>=20
> $options =3D [
>    1 =3D> 'apple',
>    2 =3D> 'orange',
>    3 =3D> 'banana',
>    4 =3D> 'caramel',
> ];
> $selected_option =3D $options[ $_GET['id'] ] ?? 'vanilla';
>=20
>=20
> Casting between arrays and objects is a whole separate issue, and =
changed
> in PHP 7.2; the RFC explains the issues quite well:
> https://wiki.php.net/rfc/convert_numeric_keys_in_object_array_casts
>=20
>=20
> Regards.
> --=20
> Rowan Tommins
> [IMSoP]