Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:109719
MIME-Version: 1.0
References: <CA+kxMuQ4ZrNEC76Mi7SxqijmwzxRrHD1ATgVrPkbZicUx7=YcQ@mail.gmail.com>
 <bbab0dfc-969c-451c-836b-77a17f176be6@www.fastmail.com>
In-Reply-To: <bbab0dfc-969c-451c-836b-77a17f176be6@www.fastmail.com>
Date: Mon, 20 Apr 2020 09:15:24 -0500
Message-ID: <CAESVnVooQoT3QzA+Xa-Tif7icw466pwmfx0tET98tnT4y2S05w@mail.gmail.com>
To: Larry Garfield <larry@garfieldtech.com>
Cc: php internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="00000000000051634905a3b9885a"
Subject: Re: [PHP-DEV] [RFC] Mixed type
From: pollita@php.net (Sara Golemon)

--00000000000051634905a3b9885a
Content-Type: text/plain; charset="UTF-8"

On Mon, Apr 20, 2020 at 8:52 AM Larry Garfield <larry@garfieldtech.com>
wrote:

> On Mon, Apr 20, 2020, at 6:17 AM, Dan Ackroyd wrote:
> > Here is an RFC for adding a 'mixed' type to the language:
> > https://wiki.php.net/rfc/mixed_type_v2
> >
>
> I am not against this, but now that we have Union types what places are
> there where the currently available type declarations are insufficient?
> Resource seems like the only remaining gap where you'd be forced to use
> `mixed` instead of a union.
>
> I imagine some type combinations get pretty wide. Like, this is verbose AF.

null|bool|int|float|string|array|object|resource

For the long term good of the language I'd prefer type aliases (or typedefs
or usings or whatever you want to call them.

use mixed = null|bool|int|float|string|array|object|resource;
use scalar = null|bool|int|float|string;
use number = int|float;

That said, baking 'mixed' in as an implicit alias of the above isn't
problematic for that future.

-Sara

--00000000000051634905a3b9885a--