Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:123730
Precedence: bulk
MIME-Version: 1.0
References: <CAPzBOBMidokE3xw251f+_qbCPAyQQRcN1WnyVF0xfuzaPBU3JA@mail.gmail.com>
 <9d28c9tOCChpWUcP1SFiFwtf2-w2XAtDzHsmM73myA7zfBsn7TxxEqs-VCnxRAgZjsk2TxS55owmM8wSLgBQL8LgeQLntUQ9toeLMkjTVx4=@gpb.moe>
 <673a1803-83c4-44b4-bd73-4ba61e83412e@app.fastmail.com> <350c1531-9bcf-4e7c-824b-8d9904b9e48e@rwec.co.uk>
 <CAPzBOBMw=Hn4SabAq0FeppLpQMwRJh2Ffc3JhhFFOps85XNazw@mail.gmail.com> <914cde73-3e53-44a8-94ff-bcf34000cc0c@processus.org>
In-Reply-To: <914cde73-3e53-44a8-94ff-bcf34000cc0c@processus.org>
Date: Fri, 21 Jun 2024 15:57:22 +0200
Message-ID: <CAPzBOBNtF=xBVRFEu3wZrMuktBV7bZzjbmBN=+6eu9qnewqmiw@mail.gmail.com>
Subject: Re: [PHP-DEV] Renaming "strict types" to "scalar type coercion"
To: Pierre <pierre-php@processus.org>
Cc: internals@lists.php.net
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
From: landers.robert@gmail.com (Robert Landers)

On Fri, Jun 21, 2024 at 3:01=E2=80=AFPM Pierre <pierre-php@processus.org> w=
rote:
>
> Le 21/06/2024 =C3=A0 14:27, Robert Landers a =C3=A9crit :
>
> This is why I wanted to work on "as" part of the pattern matching. It
> isn't clear what will happen with the actual pattern matching RFC
> (yet), but being able to do:
>
>  some_function_expecting_int($_GET['foo'] as ?int);
>
> And how about:
>
> some_function_expecting_int(\intval($_GET['foo']));
>
> And moreover, I'd write something like this, but:
>
> function validate_int(mixed $value): int {
>     if (null =3D=3D=3D $value || '' =3D=3D=3D $value) {
>         return null;
>     }
>     if (\is_int($value)) {
>         return $value;
>     }
>     if (\is_string($value) && \ctype_digit($value)) {
>         return \intval($value);
>     }
>     throw new \InvalidArgumentException("What what!");
> }
>
> some_function_expecting_int(validate_int($_GET['foo'] ?? null));
>
> But the example might be erroneous, I see your point, nevertheless making=
 coercion explicit doesn't seem really relevant to me, the one point I like=
 in your syntax would be null handling.
>
> --
>
> Pierre

Or... you could just turn off strict types instead of reinventing
coercion that isn't nearly as well documented as the built-in
coercion.

Robert Landers
Software Engineer
Utrecht NL