Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:112206
MIME-Version: 1.0
References: <CAM0CcxjEWfbnsbxYV=bp=spqg-1X0MAzBZ-RLG0WQejMvoZUTA@mail.gmail.com>
In-Reply-To: <CAM0CcxjEWfbnsbxYV=bp=spqg-1X0MAzBZ-RLG0WQejMvoZUTA@mail.gmail.com>
Date: Sun, 8 Nov 2020 15:53:08 +0100
Message-ID: <CADyq6sJwhbx47PjhiVSv69UpcqoGEHCY+-TRAaApDWh01kyoYw@mail.gmail.com>
To: Eugene Sidelnyk <zsidelnik@gmail.com>
Cc: PHP Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="00000000000024a13005b3999b10"
Subject: Re: [PHP-DEV] Union `&` operator
From: ocramius@gmail.com (Marco Pivetta)

--00000000000024a13005b3999b10
Content-Type: text/plain; charset="UTF-8"

Hey Eugene,

On Sat, Nov 7, 2020 at 4:13 PM Eugene Sidelnyk <zsidelnik@gmail.com> wrote:

> ```php
> function foo(A & B & E $object) {
>   // some work
>
>   var_dump($object);
> }
> ```
>

Fully support this for parameter, property and return types: already making
good use of intersection types since a few years.

As for when to allow them: as others have suggested in this thread, keep it
simple for now, and only allow intersection of class/interface references.

If you want to raise an RFC, special care has to be taken for the variance
in inheritance semantics.

Greets,

Marco Pivetta

http://twitter.com/Ocramius

http://ocramius.github.com/

--00000000000024a13005b3999b10--