Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:115493
MIME-Version: 1.0
References: <CAOWwgpm+PPhW6A5=Oi1tpdkQh9COGw5dQLE+Ek1p0BZ6T-xQsA@mail.gmail.com>
 <AcewfpOKliTqw3RSRafnSEC_tCXSKWHjnRVV3X953eePhs8meR7zBVFmjQjnliVfk51uFkc4COEY7pd1o4ex7bz9Gs6PCHeJAT5bfeXSRpc=@protonmail.com>
 <e5b27365-3932-4a3f-bc25-36a1dcba497c@www.fastmail.com>
In-Reply-To: <e5b27365-3932-4a3f-bc25-36a1dcba497c@www.fastmail.com>
Date: Mon, 19 Jul 2021 16:26:16 +0200
Message-ID: <CAC5V6ggN2TAqZWWkuA7fHazgBh2uQTpW5506hH88j75yDd-ndA@mail.gmail.com>
To: php internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000e2158e05c77ab8e1"
Subject: Re: [PHP-DEV] intersection types and null for defaults, properties
 and return types
From: guilliam.xavier@gmail.com (Guilliam Xavier)

--000000000000e2158e05c77ab8e1
Content-Type: text/plain; charset="UTF-8"

On Mon, Jul 19, 2021 at 4:05 PM Larry Garfield <larry@garfieldtech.com>
wrote:

>
> I can see the argument that "I need something with these two interfaces...
> or nothing" is a valid use case to care about.  However, as Saif noted,
> this is a side effect of the inability to mix union and intersection types.
>
> So, my question would be, how feasible will it be in the future to
> introduce that mixing?  If it's something that is likely to show up in 8.2
> or 8.3, we may be better off going "meh" for now and letting a solution
> fall out naturally later.  If it's something that could take a decade, then
> figuring out a way to special case "or null" in the meantime is probably
> worthwhile.  (I don't know what the best way to do that is.)
>

You made me remember that [we had non-scalar parameter type declarations
since PHP 5, and] we got scalar type declarations and return type
declarations in 7.0 but nullable type declarations "only" in 7.1 (but I
agree).

-- 
Guilliam Xavier

--000000000000e2158e05c77ab8e1--