Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:123327
Feedback-ID: i8414410d:Fastmail
User-Agent: Cyrus-JMAP/3.11.0-alpha0-456-gcd147058c-fm-hotfix-20240509.001-g0aad06e4
Precedence: bulk
MIME-Version: 1.0
Message-ID: <baffb085-d32b-4958-a773-8c11114bef3a@app.fastmail.com>
In-Reply-To: <3A6.1T4AB.9eXWvq4hof.1cHcqE@seznam.cz>
References: <3A6.1T4AB.9eXWvq4hof.1cHcqE@seznam.cz>
Date: Thu, 16 May 2024 17:58:44 -0500
To: "php internals" <internals@lists.php.net>
Subject: Re: [PHP-DEV] [RFC] [Vote] Type Guards for Classes
Content-Type: text/plain;charset=utf-8
Content-Transfer-Encoding: quoted-printable
From: larry@garfieldtech.com ("Larry Garfield")

On Thu, May 16, 2024, at 3:31 PM, Patrik V=C3=A1clavek wrote:
> Introduction
> *************
>
> This RFC proposes a new feature in PHP: type guards for classes (or=20
> interfaces). This feature aims to simplify and standardize the process=20
> of verifying that a variable is an instance of a specific class,=20
> enhancing code readability and reducing boilerplate code.

Without commenting on the idea itself, this is just a proposal at the mo=
ment.  The subject line implies there's a formal RFC now up for a vote, =
when there is not even a formal RFC yet.  Ie, please don't abuse the sub=
ject line incorrectly. :-)

To comment on the idea itself, I believe Ilija is correct that using pat=
tern matching would be the better approach here.  Right now the RFC sugg=
ests $foo as <pattern> would return true or throw, but "return $foo or t=
hrow" would indeed make more sense.  And then give us the entire power o=
f pattern matching.  (That RFC will come up formally soon(tm), I swear.)

--Larry Garfield