Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:92694
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain thefsb.org designates 173.203.187.67 as permitted sender)
User-Agent: Microsoft-MacOutlook/14.6.2.160219
Date: Sun, 24 Apr 2016 11:18:21 -0400
To: Thomas Bley <mails@thomasbley.de>
CC: <internals@lists.php.net>
Message-ID: <D34255D2.6D7EA%fsb@thefsb.org>
Thread-Topic: [PHP-DEV] [RFC] Nullable Types
References: <CAFMT4No6yFJ4r4bWGOaLZkYdpqE_YeDiEHCecq4ATBqypeUegQ@mail.gmail.com>
 <570F4BB4.6020709@zend.com>
 <57112225.6020905@thefsb.org>
 <BY2PR0201MB1784002A8F5F1D577220BD5BBF680@BY2PR0201MB1784.namprd02.prod.outlook.com>
 <57119B5E.6070205@thefsb.org>
 <BY2PR0201MB178497F586633AA99AD8E00ABF6B0@BY2PR0201MB1784.namprd02.prod.outlook.com>
 <CAKSD0w6mg5qfPZ2AexsZLppPi+hHtt9vnW2Zmfsj+A1_AMEtrg@mail.gmail.com>
 <CAFp73Xsu-+XC6aVz5Yt08HntyW3NaPm+hJYsPpoxzoqEmvxN1w@mail.gmail.com>
 <BY2PR0201MB178494E8EF85885D7AB287E6BF6D0@BY2PR0201MB1784.namprd02.prod.outlook.com>
 <20160420165307.9C86E1A83D08@dd1730.kasserver.com>
 <31.BF.14036.A61D8175@pb1.pair.com>
 <20160421163334.368CF1A80188@dd1730.kasserver.com>
In-Reply-To: <20160421163334.368CF1A80188@dd1730.kasserver.com>
Mime-version: 1.0
Content-type: text/plain;
	charset="UTF-8"
Content-transfer-encoding: quoted-printable
Subject: Re: [PHP-DEV] [RFC] Nullable Types
From: fsb@thefsb.org (Tom Worster)

Hi Thomas,

Sorry for the delay. I was traveling last week.

By convention `return;` in PHP is an early return for a function that
returns nothing at all. I think it can be confusing when reading a
function to look at a `return;` line and have to remember to look
elsewhere to discover what that means. And it can mean something different
in every function.

I prefer to write functions that return only the declared type. In some
cases I need to write functions that return only the declared type or
null. That's the limit of what I think PHP 7.1 should provide.

Hence, for me this has no attraction but it does introduce new ways to
write bugs. So I am not enthusiastic.

Tom


On 4/21/16, 12:33 PM, "Thomas Bley" <mails@thomasbley.de> wrote:

>Hello Tom,
>
>with default return value I mean to return a certain value if nothing
>else is returned (similar to method parameters with a default value).
>
>example 1:
>
>declare(strict_types=3D0);
>
>function my_strpos(string $haystack, string $needle): int =3D false {
>  return 42; // return 42
>  return false; // return false
>  return true; // return 1
>  return; // return false
>}
>
>example 2:
>
>declare(strict_types=3D1);
>
>function my_strpos(string $haystack, string $needle): int =3D false {
>  return 42; // return 42
>  return false; // return false
>  return true; // fatal error
>  return; // return false
>}
>
>Regards
>Thomas
>
>
>fsb@thefsb.org wrote on 21.04.2016 15:05:
>
>> Hi Thomas,
>>=20
>>=20
>> What is a default return declaration? Is this for branches within the
>>function
>> that do not lead to a return statement?
>>=20
>>=20
>> Tom
>>=20
>>=20
>>=20
>>=20
>>=20
>> From: Thomas Bley
>> Sent: =E2=80=8EWednesday=E2=80=8E, =E2=80=8EApril=E2=80=8E =E2=80=8E20=E2=80=8E, =E2=80=8E2016 =E2=80=8E12=E2=80=8E:=E2=80=8E53=E2=80=8E =E2=
=80=8EPM
>> To: guilhermeblanco@gmail.com, cornelius.howl@gmail.com, dmitry@zend.com
>> Cc: fsb@thefsb.org, internals@lists.php.net
>>=20
>>=20
>>=20
>>=20
>>=20
>> What do you think about default return values?
>>=20
>> e.g.
>>=20
>> function foo(): db_result =3D null {
>> }
>>=20
>> function canLogin(): bool =3D false {
>> }
>