Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:113524
To: internals@lists.php.net
References: <CAOkcCt88CD0aAZ=+5Oi7SeW7E3Z1OLvai=s4s-MUQq6QwD1z5w@mail.gmail.com>
 <CAKuGYLRZEieMfOe1eYYkZnTaWm8yGHP8UbrEfwrg4ZReDX3NTQ@mail.gmail.com>
Message-ID: <d7c8ffb2-8eea-0fa3-a35f-8333c88a12fc@gmail.com>
Date: Sun, 14 Mar 2021 22:09:02 +0000
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101
 Thunderbird/78.8.0
MIME-Version: 1.0
In-Reply-To: <CAKuGYLRZEieMfOe1eYYkZnTaWm8yGHP8UbrEfwrg4ZReDX3NTQ@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-GB
Subject: Re: [PHP-DEV] [RFC Proposal] Allow methods to 'become' static
From: rowan.collins@gmail.com (Rowan Tommins)

On 14/03/2021 19:40, Matthew Brown wrote:
> It's maybe possible in the special case of implementing interfaces, but
> it's unsound for general inheritance:
>
> <?php
>
> class A {
>      public int $someInt = 0;
>
>      public function getSomeInt() : int {
>          return $this->someInt;
>      }
> }
>
> class B extends A {
>      public static function getSomeInt() : int {
>          return parent::getSomeInt();
>      }
> }


Can you explain what this is illustrating? Right now, it doesn't 
compile, but that's what Gert was suggesting be changed, so the 3v4l 
link isn't very enlightening.

 From the point of view of the contract of the class, it's fine: 
$foo->getSomeInt() is still a legal call if $foo is actually an instance 
of B.

Are you saying that having the parent::getSomeInt() call fail would be 
problematic?

Regards,

-- 
Rowan Tommins
[IMSoP]