Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:99216
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.50 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <8de6a2ef-9602-e489-f19c-001005626b87@gmail.com>
References: <CADqTB_jB2ic4jx84HXVBPDr2qbP-DnXe782quKwc6o-ERpJJVw@mail.gmail.com>
 <CANUQDCjpjz8Wret1D6q9wb8rfBH4Xqc4uDqLTtuptkUdesUK4g@mail.gmail.com>
 <CADqTB_gbhw+pr+8dpkwdFwRTjiY4pk6fyeTnLUv72fBjTpArZA@mail.gmail.com>
 <CA+kxMuS=xBVQdyObpU2yK1jtr+3=JmAPJK-DaRKCZdCZRCfp2w@mail.gmail.com>
 <CADqTB_hs85GU63D5pB7ArHBhJ=0CK_aUYtPiOvokn4OeyFXTRA@mail.gmail.com>
 <CANUQDChF3BVkBUH7BOjXwNQapvzBQHwExZMQbeRYpn44jcCXfA@mail.gmail.com>
 <CADqTB_gc9BJnhL7fE-w51dYX760GSGsu6Vhc2d=DStLWRKXLRA@mail.gmail.com> <8de6a2ef-9602-e489-f19c-001005626b87@gmail.com>
Date: Sun, 28 May 2017 18:06:47 +0100
Message-ID: <CALtMV+PBbVjue=26-=W5K7PwHA=hjjRQqKKaxq-KJ6W2doDkwA@mail.gmail.com>
To: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="001a114691408ec74205509898c2"
Subject: Re: [PHP-DEV] Parameter type widening RFC
From: aidantwoods@gmail.com (Aidan Woods)

--001a114691408ec74205509898c2
Content-Type: text/plain; charset="UTF-8"

So, if I understand everything here correctly

```
interface Foo
{
  public function bar(Boo $Boo);
}
```

and

```
interface Foo
{
  /*
   * @param $Boo, pretty please accept type Boo here
   */
  public function bar($Boo);
}
```

will be equivalent in 7.2? :(

Regards,
Aidan

On 28 May 2017 at 16:49, Rowan Collins <rowan.collins@gmail.com> wrote:

> On 28/05/2017 14:25, Rasmus Schultz wrote:
>
>> With an explicit mixed type-hint, you can still achieve what you want
>>
>
> You are making a valid point in general, but you clearly haven't read or
> understood the explanations you've been given why an explicit mixed
> type-hint will NOT achieve what the authors of this RFC wanted.
>
> If an existing class implements a library's interface, or extends a
> library's base class, with no type hint, then the library currently has to
> break both backward and forward compatibility to add type hints: the user
> of the library will *have to* add the type hints to their implementation,
> and once they do so, they will *have to* require that minimum version of
> the library.
>
> If the user of the library has to add "mixed" to all their method
> signatures to use the now-type-hinted library, the library still has to
> declare a breaking change, so that feature would not help this use case,
> even if it would be better in others.
>
> Regards,
>
> --
> Rowan Collins
> [IMSoP]
>
>
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>

--001a114691408ec74205509898c2--