Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:75458
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain ajf.me designates 192.64.116.199 as permitted sender)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
In-Reply-To: <CAGAGxbZG+c46P4E2pmEHNnEv=4DyTrHOuXbZu3zAOSU3M6-A-A@mail.gmail.com>
Date: Mon, 14 Jul 2014 14:36:42 +0100
Cc: PHP internals <internals@lists.php.net>
Content-Transfer-Encoding: quoted-printable
Message-ID: <05CE2216-C5D9-4937-9F2E-AA1407284D9F@ajf.me>
References: <08503591-EFC8-48E6-984E-FFC292C5EA5F@ajf.me> <16D48604-0C0A-4613-91A4-21392E3A2636@ajf.me> <CAGAGxbZG+c46P4E2pmEHNnEv=4DyTrHOuXbZu3zAOSU3M6-A-A@mail.gmail.com>
To: Chris Wright <daverandom@php.net>
Subject: Re: [PHP-DEV] [RFC] Scalar Type Hinting With Casts (re-opening)
From: ajf@ajf.me (Andrea Faulds)


On 14 Jul 2014, at 14:33, Chris Wright <daverandom@php.net> wrote:

> 2) A common-ish use case here would be:
>=20
>   function foo(bool $bool) {}
>   foo($flags & A_FLAG);
>=20
> The intent of the expression $flags & A_FLAG is obvious to the reader
> as fetching a boolean, but the result will often be an integer that is
> neither 1 nor 0. This cannot be handled by foo((bool)$flags & A_FLAG);
> because of precedence, foo((bool)($flags & A_FLAG)); is messy. Andrea
> suggested foo($flags & A_FLAG !=3D 0); which is better but still a
> little messy.
>=20
> Personally I would rather just accept data loss and stay consistent
> with the rest of the language (i.e. condition evaluation), but I do
> understand the PoV of those resistant to it.

Yeah, that=92s the problem for me. I want things like ($flags & A_FLAG) =
to work, but I don=92t want =93foo=94 to work.

I suggested on IRC that empty strings, TRUE, FALSE, NULL, and values =
that validate for the int type hint could be accepted. Is that a good =
idea? Though it feels a bit loose, I think it covers all the important =
common use cases.

--
Andrea Faulds
http://ajf.me/