Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:109641
Message-ID: <436FD800-A316-4C99-8793-C6EF4BD15BE3@gmail.com>
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_FC621D49-FD78-4597-AC2E-F5E2EA282FC0"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.80.23.2.2\))
Date: Tue, 14 Apr 2020 19:45:16 +0200
In-Reply-To: <CAF+90c8wKkaT_2NdeHB0VOUmBnAEfaKsBDbaOEa1s8Z_arPyPA@mail.gmail.com>
Cc: Nicolas Grekas <nicolas.grekas+php@gmail.com>,
 Gabriel Caruso <carusogabriel34@gmail.com>,
 PHP Internals <internals@lists.php.net>
To: Nikita Popov <nikita.ppv@gmail.com>
References: <CAP=4hC+9duSVcREvwOD3jZv+5fmqQzzR=UEraw4Yr6P+b+FfaQ@mail.gmail.com>
 <90F4B395-F010-4196-9C40-7896D4F3F2F4@gmail.com>
 <CAP=4hC+moKGF-XyGuaYEzc54tJb++5bUxCpF-8vXxsPS+NHuUw@mail.gmail.com>
 <CAP=4hCLH9PrkQxuF=m154jA2+d56eTXTfmtsCfjxOcBiR4pmsw@mail.gmail.com>
 <CAP=4hCLLY5THWuR1h-hiTQ4sW0Nb1Wv1+EYcSBhmaTYU6x7MOg@mail.gmail.com>
 <CAOWwgpmXfzDw4yWUEme_DtuiMitZf6vqYVm57F_nxYAAHPyORA@mail.gmail.com>
 <CAP=4hC+cxqXp-TLUUeRWg0q5=Bzi5dXMr_N7ypfVjTywP6zF1Q@mail.gmail.com>
 <CAOWwgpmK8Zzk4+LAnSFW0nTCR8qEaFG4AD_97zoDqvA7wh6kyA@mail.gmail.com>
 <0A374409-6FA6-4E02-A7E6-EACA3E42451C@gmail.com>
 <CAF+90c8wKkaT_2NdeHB0VOUmBnAEfaKsBDbaOEa1s8Z_arPyPA@mail.gmail.com>
Subject: Re: [PHP-DEV] [RFC] [DISCUSSION] Ensure correct magic methods'
 signatures when typed
From: claude.pache@gmail.com (Claude Pache)

--Apple-Mail=_FC621D49-FD78-4597-AC2E-F5E2EA282FC0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8



> Le 14 avr. 2020 =C3=A0 18:53, Nikita Popov <nikita.ppv@gmail.com> a =
=C3=A9crit :
>=20
> On Tue, Apr 14, 2020 at 6:07 PM Claude Pache <claude.pache@gmail.com =
<mailto:claude.pache@gmail.com>> wrote:
>=20
>=20
> > Le 14 avr. 2020 =C3=A0 16:54, Nicolas Grekas =
<nicolas.grekas+php@gmail.com <mailto:nicolas.grekas%2Bphp@gmail.com>> a =
=C3=A9crit :
> >=20
> > I'm just not sold on allowing "void" on __construct, because the =
very concept of a return type on a constructor is ... void, and also =
because of the code style choices this will open (and the CS "wars" I =
mentioned).
> >=20
>=20
> This issue is not specific to magic method like __construct(). It is =
the whole concept of =E2=80=9Cvoid=E2=80=9D as return type which is, =
say, =E2=80=9Cproblematic=E2=80=9D.
>=20
> In fact, =E2=80=9Cvoid=E2=80=9D is not really a return type. It is a =
way to state that the method is not supposed to return anything, which =
means, as you said very well, that =E2=80=9Cthe very concept of return =
type on [this method] is void=E2=80=9D.
>=20
> That might be a reason to reject the concept of =E2=80=9Cvoid=E2=80=9D =
as return type. Or to revive =
https://wiki.php.net/rfc/allow-void-variance =
<https://wiki.php.net/rfc/allow-void-variance> =
<https://wiki.php.net/rfc/allow-void-variance =
<https://wiki.php.net/rfc/allow-void-variance>> . But again, the issue =
is orthogonal to the fact that this particular method is magic, and we =
should not cherry-pick and reject the concept of =E2=80=9Cvoid=E2=80=9D =
for __construct() and similar magic methods only.
>=20
> Constructors not having a return type is standard behavior across most =
(all?) languages. You can't specify a constructor return type in C++. =
You can't specify one in C#. You can't specify one in Java. Off-hand, I =
can't name a language that both has a first-class constructor concept =
(Rust's "new" idiom does not count) and specifies a return type on it.
>=20
> It would naturally follow that, yes, you can't specify a constructor =
return type in PHP either, just like we enforce right now. Unless we =
have some strong reason to deviate from standard behavior that I do not =
see?
>=20
> Regards,
> Nikita

Do those languages allow to return something from the constructor (as =
does PHP currently)? because I=E2=80=99m more interested in the =
semantics of `: void` than the exact way to have it.

=E2=80=94Claude


--Apple-Mail=_FC621D49-FD78-4597-AC2E-F5E2EA282FC0--