Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:123728
Feedback-ID: id5114917:Fastmail
User-Agent: Cyrus-JMAP/3.11.0-alpha0-522-ga39cca1d5-fm-20240610.002-ga39cca1d
Precedence: bulk
MIME-Version: 1.0
Message-ID: <a65f9149-a58d-4798-b3b2-2e3a8755520c@app.fastmail.com>
In-Reply-To: <914cde73-3e53-44a8-94ff-bcf34000cc0c@processus.org>
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>
Date: Fri, 21 Jun 2024 14:16:26 +0100
To: internals@lists.php.net
Subject: Re: [PHP-DEV] Renaming "strict types" to "scalar type coercion"
Content-Type: multipart/alternative;
 boundary=038c512fb6054b429fa43f2452b85dc8
From: imsop.php@rwec.co.uk ("Rowan Tommins [IMSoP]")

--038c512fb6054b429fa43f2452b85dc8
Content-Type: text/plain;charset=utf-8
Content-Transfer-Encoding: quoted-printable

> 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:
>>=20
>>  some_function_expecting_int($_GET['foo'] as ?int);


I've started drafting a proposal for strict casts - independent of the p=
attern matching effort, but might be combinable - but the devil's in the=
 details of exactly when the cast should fail, and what should happen wh=
en it does.

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=
 settled on a full proposal yet.



On Fri, 21 Jun 2024, at 13:46, Pierre wrote:
>=20
> And how about:
>=20
> some_function_expecting_int(\intval($_GET['foo']));


intval($foo) and (int)$foo do exactly the same thing; they're basically =
just different syntax.


>=20
> And moreover, I'd write something like this, but:
>=20
> function validate_int(mixed $value): int { ...


Which is why I included the word *concise*: it shouldn't be necessary fo=
r every user to write or install a custom function for such a common req=
uirement.

Regards,
--=20
Rowan Tommins
[IMSoP]
--038c512fb6054b429fa43f2452b85dc8
Content-Type: text/html;charset=utf-8
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE html><html><head><title></title><style type=3D"text/css">p.Mso=
Normal,p.MsoNoSpacing{margin:0}</style></head><body><blockquote type=3D"=
cite" id=3D"qt" style=3D""><div class=3D"qt-moz-cite-prefix"><div class=3D=
"qt-moz-cite-prefix">Le 21/06/2024 =C3=A0 14:27, Robert Landers a
      =C3=A9crit&nbsp;:<br></div><blockquote type=3D"cite" cite=3D"mid:C=
APzBOBMw=3DHn4SabAq0FeppLpQMwRJh2Ffc3JhhFFOps85XNazw@mail.gmail.com"><pr=
e class=3D"qt-moz-quote-pre">This is why I wanted to work on "as" part o=
f 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);<br></pre></blockquot=
e></div></blockquote><div><br></div><div><br></div><div>I've started dra=
fting a proposal for strict casts - independent of the pattern matching =
effort, but might be combinable - but the devil's in the details of exac=
tly when the cast should fail, and what should happen when it does.<br><=
/div><div><br></div><div>For instance, should cast('abc' as ?int) fail, =
or default to null? Do we need different syntax for both? I have some th=
oughts, but haven't quite settled on a full proposal yet.<br></div><div>=
<br></div><div><br></div><div><br></div><div>On Fri, 21 Jun 2024, at 13:=
46, Pierre wrote:<br></div><blockquote type=3D"cite" id=3D"qt" style=3D"=
"><div class=3D"qt-moz-cite-prefix">
<br></div><p>And how about:<br></p><pre>some_function_expecting_int(\int=
val($_GET['foo']));<br></pre></blockquote><div><br></div><div><br></div>=
<div>intval($foo) and (int)$foo do exactly the same thing; they're basic=
ally just different syntax.<br></div><div><br></div><div><br></div><bloc=
kquote type=3D"cite" id=3D"qt" style=3D""><pre><br></pre><p>And moreover=
, I'd write something like this, but:<br></p><pre>function validate_int(=
mixed $value): int { ...<br></pre></blockquote><div><br></div><div><br><=
/div><div>Which is why I included the word *concise*: it shouldn't be ne=
cessary for every user to write or install a custom function for such a =
common requirement.<br></div><div><br></div><div>Regards,<br></div><div>=
-- <br></div><div>Rowan Tommins<br></div><div>[IMSoP]<br></div></body></=
html>
--038c512fb6054b429fa43f2452b85dc8--