Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:101429
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.41 as permitted sender)
Date: Wed, 27 Dec 2017 09:50:54 +0000
User-Agent: K-9 Mail for Android
In-Reply-To: <c126a971-f671-1dc8-384b-4338765996da@rhsoft.net>
References: <72392123-d37b-26df-6886-218f48205f8a@fleshgrinder.com> <fab1b1a0-d920-4a68-7ca0-0a0dd9b82332@rhsoft.net> <6894aa94-0400-7a9a-f00c-47f1f556a4d0@php.net> <2241495.C7RNBcXJNU@vulcan> <c126a971-f671-1dc8-384b-4338765996da@rhsoft.net>
MIME-Version: 1.0
Content-Type: text/plain;
 charset=utf-8
Content-Transfer-Encoding: quoted-printable
To: internals@lists.php.net
Message-ID: <58A5ABDF-AA25-46D4-83E7-4DE72E3DFF5E@gmail.com>
Subject: Re: [PHP-DEV] [RFC] [DISCUSSION] Scalar Pseudo-type
From: rowan.collins@gmail.com (Rowan Collins)

On 26 December 2017 18:35:29 GMT+00:00, "lists@rhsoft=2Enet" <lists@rhsoft=
=2Enet> wrote:
>
>
>Am 26=2E12=2E2017 um 19:18 schrieb Larry Garfield:
>> If I may, I think the argument has always been that
>>=20
>> 1) Foo & Bar makes total sense
>> 2) int|float makes total sense
>> 3) int & string is illogical so wouldn't matter anyway
>
>not true
>
>function x(int|string $x)
>{
>  $x =3D (int)$x;
>}

I think there's a misunderstanding here=2E Some previous proposals for "un=
ion types" also included "intersection types", so that you could assert "pa=
rameter must implement both of these interfaces"=2E So 'Foo|Bar $x' would m=
ean '$x instanceof Foo || $x instanceof Bar' and 'Foo&Bar $x' would mean '$=
x instanceof Foo && $x instanceof Bar'=2E

I presume that's what Larry means by "int & string is illogical", because =
it would translate to "is_int($x) && is_string($x)", which is false for all=
 values of $x=2E This is different from "int | string", which, as you say, =
might have valid uses=2E

Regards,

--=20
Rowan Collins
[IMSoP]