Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:123737
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> <a65f9149-a58d-4798-b3b2-2e3a8755520c@app.fastmail.com>
In-Reply-To: <a65f9149-a58d-4798-b3b2-2e3a8755520c@app.fastmail.com>
Date: Fri, 21 Jun 2024 18:24:55 +0200
Message-ID: <CAPzBOBN5n7uyxU_X8Q5MxTJ49G9FQdH6-Meyv4i2QYhVyw5aWA@mail.gmail.com>
Subject: Re: [PHP-DEV] Renaming "strict types" to "scalar type coercion"
To: "Rowan Tommins [IMSoP]" <imsop.php@rwec.co.uk>
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 4:50=E2=80=AFPM Rowan Tommins [IMSoP]
<imsop.php@rwec.co.uk> wrote:
>
> 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);
>
>
>
> I've started drafting a proposal for strict casts - independent of the pa=
ttern matching effort, but might be combinable - but the devil's in the det=
ails of exactly when the cast should fail, and what should happen when it d=
oes.
>
> For instance, should cast('abc' as ?int) fail, or default to null? Do we =
need different syntax for both? I have some thoughts, but haven't quite set=
tled on a full proposal yet.

I know we have different opinions about many things, but I'd actually
love to help if you'd want it. I think our different opinions might
make it better. :)

I vaguely remember our last conversation about this and I kinda liked
your 'catch' thing. IIRC, it looked something like:

'abc' as ?int otherwise false;

or something (pretty sure it wasn't "otherwise") where if it wasn't an
int|null, it would fall back to false. If there wasn't a fallback, it
was a TypeError or something?

One thing nice about "as" is that having typed variables becomes much
more simpler to implement (if anyone wanted to implement it) even as a
transpilation step:

int $x =3D 5;

$x +=3D "10"; // type error

gets transpiled to:

$x =3D 5 as int;

$x +=3D "10" as int;

Interesting stuff.

>
> On Fri, 21 Jun 2024, at 13:46, Pierre wrote:
>
>
> And how about:
>
> some_function_expecting_int(\intval($_GET['foo']));
>
>
>
> intval($foo) and (int)$foo do exactly the same thing; they're basically j=
ust different syntax.
>
>
>
> And moreover, I'd write something like this, but:
>
> function validate_int(mixed $value): int { ...
>
>
>
> Which is why I included the word *concise*: it shouldn't be necessary for=
 every user to write or install a custom function for such a common require=
ment.
>
> Regards,
> --
> Rowan Tommins
> [IMSoP]

Robert Landers
Software Engineer
Utrecht NL