Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:109723
MIME-Version: 1.0
References: <CA+kxMuQ4ZrNEC76Mi7SxqijmwzxRrHD1ATgVrPkbZicUx7=YcQ@mail.gmail.com>
 <bbab0dfc-969c-451c-836b-77a17f176be6@www.fastmail.com> <CAESVnVooQoT3QzA+Xa-Tif7icw466pwmfx0tET98tnT4y2S05w@mail.gmail.com>
In-Reply-To: <CAESVnVooQoT3QzA+Xa-Tif7icw466pwmfx0tET98tnT4y2S05w@mail.gmail.com>
Date: Mon, 20 Apr 2020 17:59:02 +0200
Message-ID: <CAC5V6gjOPO1D9ZgU_hmyGbpi41Tf-OyxxL_1+21ax-OGJ_2NTg@mail.gmail.com>
To: Sara Golemon <pollita@php.net>
Cc: Larry Garfield <larry@garfieldtech.com>, php internals <internals@lists.php.net>
Content-Type: text/plain; charset="UTF-8"
Subject: Re: [PHP-DEV] [RFC] Mixed type
From: guilliam.xavier@gmail.com (Guilliam Xavier)

On Mon, Apr 20, 2020 at 4:15 PM Sara Golemon <pollita@php.net> wrote:
>
> 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.

The `scalar` example should be `bool|int|float|string`, without `null`.
And for `mixed`, as already said, we cannot use `resource` in union types.

All the more reason to standardize those "aliases" in core?

--
Guilliam Xavier