Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:114081
MIME-Version: 1.0
References: <CAH5C8xUqzFJ4V0uo7_FviMq3Sy9Da3MWNMhh+neMO8ZjEnyQWg@mail.gmail.com>
 <CAF+90c8s0+GvL378hhxnah315ae69_56LO=pMXnQisA5-E-5Lw@mail.gmail.com> <918bd585-0a5a-063d-7d4e-c89eadef0dde@processus.org>
In-Reply-To: <918bd585-0a5a-063d-7d4e-c89eadef0dde@processus.org>
Date: Tue, 20 Apr 2021 11:44:54 +0200
Message-ID: <CAH5C8xVqvOJfN1xqjHJVrQaSPCeiJBUvf+_jvhXGC=4O5-kdRg@mail.gmail.com>
To: Pierre <pierre-php@processus.org>
Cc: PHP Internals List <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="00000000000010d1e805c0644d5b"
Subject: Re: [PHP-DEV] [RFC] [Discussion] Adding return types to internal methods
From: kocsismate90@gmail.com (=?UTF-8?B?TcOhdMOpIEtvY3Npcw==?=)

--00000000000010d1e805c0644d5b
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi Pierre,

Having type-inference wouldn't transparently fix some of these issues ?
>
> Let's consider a method such as foo($array) which returns a bool or a
> string, for example. And suddenly, the types get specified as foo(?array
> $array): bool|string.
>

PHP doesn't have such an advanced type inference capability: just consider
dynamic calls, or regular function invocations
where the return type information is not available.

On the other hand, we could add return types implicitly, as it was proposed
earlier, but I didn't really like this solution.
For a little more details, have a look at my initial message:
https://externals.io/message/112625#112625 Besides, I think
it's better to document the return types explicitly as a declaration, since
they usually help during implementation.

M=C3=A1t=C3=A9

--00000000000010d1e805c0644d5b--