Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:117581
MIME-Version: 1.0
References: <CAFPFaMLgtm04xwgPsrUBXtOCNRwKgDv5oiiS7aPRr0sqMd4+_g@mail.gmail.com>
 <CADyq6sJnKB4+02rZ6LvZfoAnX9OrHmhQko1FqEyR5Qu6Uj7asQ@mail.gmail.com>
In-Reply-To: <CADyq6sJnKB4+02rZ6LvZfoAnX9OrHmhQko1FqEyR5Qu6Uj7asQ@mail.gmail.com>
Date: Sat, 23 Apr 2022 19:25:14 +0100
Message-ID: <CAFPFaMLxKOEpmJADd6gGgCy=sd6SiLiKOvAEYOYYh3uNgyQD+w@mail.gmail.com>
To: Marco Pivetta <ocramius@gmail.com>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000806dad05dd56770b"
Subject: Re: [PHP-DEV] Canonicalize "iterable" into "array|Traversable" and Reflection
From: george.banyard@gmail.com ("G. P. B.")

--000000000000806dad05dd56770b
Content-Type: text/plain; charset="UTF-8"

On Sat, 23 Apr 2022 at 19:19, Marco Pivetta <ocramius@gmail.com> wrote:

> Hey George,
>
> How would the engine behave (with this RFC included) with an inheritance
> check?
>
> Specifically:
>
> interface A {
>     function foo(interable $param): iterable;
> }
> interface B {
>     function foo(array|\Trabersable $param): array|\Traversable:
> }
>
> Would they be compatible with each other, if put in inheritance between
> each other in any order?
>

They would, that's the main point of this change is to make handling this
sort of code easier.
As currently we need to manually check that array is indeed compatible with
iterable and similarly with Traversable.

With this change, the engine would effectively see:

interface A {
    function foo(array|\Traversable $param): array|\Traversable;
}
interface B {
    function foo(array|\Trabersable $param): array|\Traversable:
}

Allowing us to use the generic LSP handling (and in this case it is trivial)

--000000000000806dad05dd56770b--