Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:116228
MIME-Version: 1.0
References: <CAFPFaM+M5gtCmGZrOZdH0zatS-472_xVodhw6EoU0z3mPxNyYw@mail.gmail.com>
 <CAAKU0umCQsdDNeasvDxZHTjGpHdKht=_uyzhbjJ96h+-ih_5PQ@mail.gmail.com>
 <CAF+90c8d0+m6W0hajBSqGF6+nbzUrXQ5vghx4bO69qq5By53PA@mail.gmail.com> <4638866.snJnjoNyIA@tempete>
In-Reply-To: <4638866.snJnjoNyIA@tempete>
Date: Tue, 5 Oct 2021 16:47:36 +0200
Message-ID: <CANS-=pcFDebXj-9FuAv+01WjGvJUygMwQA0=K46NwKtjOFHpnQ@mail.gmail.com>
To: =?UTF-8?Q?C=C3=B4me_Chilliet?= <come@chilliet.eu>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000d063dc05cd9c1d8f"
Subject: Re: [PHP-DEV] [RFC] Allow null as standalone type
From: kjarli@gmail.com (Lynn)

--000000000000d063dc05cd9c1d8f
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Tue, Oct 5, 2021 at 4:08 PM C=C3=B4me Chilliet <come@chilliet.eu> wrote:

>
> Why would function a(): null|false {} be legal but function b(): null|0
> would not?
>
> This is inconsistent to me. And adding null, then false, then true for th=
e
> sake of completeness feels like avoiding to treat the static value as typ=
e
> hint subject.
>

I'm not opposed to having values that aren't objects. Feels like a
shorthand notation of enums, or the subset thereof.

```php
function getType(): 'dropdown'|'textfield';
function getExitCode(): 0|1|255;
```

--000000000000d063dc05cd9c1d8f--