Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:97106
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmx.de designates 212.227.17.22 as permitted sender)
To: Niklas Keller <me@kelunik.com>, PHP Internals <internals@lists.php.net>
References: <CANUQDCg+g5toVyi5VKCSkgvot0tM2Vr-UmZ=uYLYOqLPd+9+vg@mail.gmail.com>
Message-ID: <05c849b4-5d84-f77b-7fdb-09ecbe9dc07e@gmx.de>
Date: Mon, 21 Nov 2016 12:59:14 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101
 Thunderbird/45.5.0
MIME-Version: 1.0
In-Reply-To: <CANUQDCg+g5toVyi5VKCSkgvot0tM2Vr-UmZ=uYLYOqLPd+9+vg@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Subject: Re: [RFC] Parameter No Type Variance
From: cmbecker69@gmx.de ("Christoph M. Becker")

On 21.11.2016 at 10:39, Niklas Keller wrote:

> I'd like to announce a RFC to allow omitting the type declarations for
> parameters in subclasses:
> https://wiki.php.net/rfc/parameter-no-type-variance
> 
> PHP doesn't currently allow variance for parameters as checking these for
> compatibility isn't possible on compile time.
> This limitation is caused by autoloading and doesn't allow widening the
> accepted parameters.
> 
> This RFC proposes to allow ommiting the type entirely in a subclass, as
> dropping all parameter constraints is
> always valid according to the LSP principle.

Have you considered that instead of simply omitting the type
declaration, one would have to mark the omission explicitly, to still
get a compile time warning in case of unintended omission?

-- 
Christoph M. Becker