Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:114099
MIME-Version: 1.0
References: <CAH5C8xX87sVh5NDuQ1EfeEbSxdHawO5yNfk5zHEToAqYGJa7=Q@mail.gmail.com>
 <CADyq6sJ5StVLhgEW86xXcVeETTBUodXWrFkv0Lpin+9+du_WJg@mail.gmail.com>
 <CAF+90c8BJ5Fm05ON8_1WU6oWrgXKk49ynfO+axLJU8MqLhY_-Q@mail.gmail.com> <CADyq6sJ+0jiGca64wyVqHGxJOxmnCnKc8W5CTmoyFJMAS6kQnA@mail.gmail.com>
In-Reply-To: <CADyq6sJ+0jiGca64wyVqHGxJOxmnCnKc8W5CTmoyFJMAS6kQnA@mail.gmail.com>
Date: Thu, 22 Apr 2021 12:15:37 +0200
Message-ID: <CAH5C8xWEmzcbmawgtdMN+PC1mjFx0PS9+AQepztuThQwqEDm2Q@mail.gmail.com>
To: Marco Pivetta <ocramius@gmail.com>
Cc: Nikita Popov <nikita.ppv@gmail.com>, PHP Internals List <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="0000000000008b7fed05c08cf6e7"
Subject: Re: [PHP-DEV] [RFC] [Vote] Adding return types to internal methods
From: kocsismate90@gmail.com (=?UTF-8?B?TcOhdMOpIEtvY3Npcw==?=)

--0000000000008b7fed05c08cf6e7
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

>
> Overall, I see the change of reported `ReflectionMethod#getReturnType()`
> as non-problematic, and tooling around reflection would continue working =
as
> expected, while adding new API requires:
>

I do think it would be problematic, and a new API is a must (either the one
Nikita asked about or the current one). Let's consider a reflection-based
static analyser: in PHP 8.1, it would report the incompatible
user-land return types as a very serious issue all of a sudden, while in
fact it's not the case yet.

(now I see that Nikita answered the same)

M=C3=A1t=C3=A9

>

--0000000000008b7fed05c08cf6e7--