Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:104312
MIME-Version: 1.0
References: <CADqTB_gteykpHroN8MFLuMEFsh+oNmZ3RhsGvBx_yY-5zGvnJg@mail.gmail.com>
 <c47773b6-55de-e4f2-f34e-f155062272d4@korulczyk.pl> <CADyq6sLkDrS-D7wbOsyKzo9s4jw1neXO9bp73X6tY=DYJ5JBEw@mail.gmail.com>
 <695e24fe-386f-c11a-4bd3-81129cb9ffe2@korulczyk.pl> <CADyq6sKTqXcmeECjgsz=sMog6wV=ZYCJ_kLk1Kge8F66KDT+fA@mail.gmail.com>
 <42a5e3cb-358a-3e8e-0985-099263a57374@korulczyk.pl>
In-Reply-To: <42a5e3cb-358a-3e8e-0985-099263a57374@korulczyk.pl>
Date: Fri, 8 Feb 2019 13:22:59 +0100
Message-ID: <CADyq6sKtTjZ=mQK+gjceh7bMhujpuNLb_-LbCoqtDH1-_7NW=w@mail.gmail.com>
To: Robert Korulczyk <robert@korulczyk.pl>
Cc: Rasmus Schultz <rasmus@mindplay.dk>, PHP Internals List <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000c4f5f3058161053c"
Subject: Re: [PHP-DEV] Mixed type-hint
From: ocramius@gmail.com (Marco Pivetta)

--000000000000c4f5f3058161053c
Content-Type: text/plain; charset="UTF-8"

On Fri, 8 Feb 2019, 13:13 Robert Korulczyk <robert@korulczyk.pl wrote:

> Sounds like an arbitrary interpretation. Treating `?mixed" as "top type"
> (including null) would be more practical and consistent with other
> type-hints.
>

The PHP ecosystem (libraries) already uses `mixed` as a type including
`null`. You can survey for usages of `mixed|null`, which is currently
normalised to `mixed` by existing static analysis tooling (psalm, phpstan).

Even then, by adding a non-nullable almost-top-type doesn't seem helpful:
"here's something random, just make sure it isn't null". That's something
more interesting for an eventual union type RFC (revival?).

Could you clarify on a use-case for changing the semantics of `mixed`?

>

--000000000000c4f5f3058161053c--