Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:123727
Content-Type: multipart/alternative;
 boundary="------------69XBQYOWbjSy9dDdk2hq0h4S"
Message-ID: <914cde73-3e53-44a8-94ff-bcf34000cc0c@processus.org>
Date: Fri, 21 Jun 2024 14:46:53 +0200
Precedence: bulk
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: [PHP-DEV] Renaming "strict types" to "scalar type coercion"
To: internals@lists.php.net
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>
Content-Language: fr-FR, en-US
In-Reply-To: <CAPzBOBMw=Hn4SabAq0FeppLpQMwRJh2Ffc3JhhFFOps85XNazw@mail.gmail.com>
From: pierre-php@processus.org (Pierre)

This is a multi-part message in MIME format.
--------------69XBQYOWbjSy9dDdk2hq0h4S
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit

Le 21/06/2024 à 14:27, Robert Landers a écrit :
> 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 === $value || '' === $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

--------------69XBQYOWbjSy9dDdk2hq0h4S
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit

<!DOCTYPE html>
<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <div class="moz-cite-prefix">Le 21/06/2024 à 14:27, Robert Landers a
      écrit :<br>
    </div>
    <blockquote type="cite"
cite="mid:CAPzBOBMw=Hn4SabAq0FeppLpQMwRJh2Ffc3JhhFFOps85XNazw@mail.gmail.com">
      <pre class="moz-quote-pre" wrap="">
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);
</pre>
    </blockquote>
    <p>And how about:</p>
    <pre>some_function_expecting_int(\intval($_GET['foo']));</pre>
    <p>And moreover, I'd write something like this, but:</p>
    <pre>function validate_int(mixed $value): int {
    if (null === $value || '' === $value) {
        return null;
    }
    if (\is_int($value)) {
        return $value;
    }
    if (\is_string($value) &amp;&amp; \ctype_digit($value)) {
        return \intval($value);
    }
    throw new \InvalidArgumentException("What what!");
}

some_function_expecting_int(validate_int($_GET['foo'] ?? null));

</pre>
    <p>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.</p>
    <p>--</p>
    <p>Pierre<br>
    </p>
  </body>
</html>

--------------69XBQYOWbjSy9dDdk2hq0h4S--