Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:130043
Subject: Re: [PHP-DEV] [IDEA for RFC] let the "new" operator fail when the
 __construct() function returns a value.
To: internals@lists.php.net
References: <CAFgk54k4NkUrUkMD=HE1TkowDJb55X9B7hcCa7vxGUbAfQhv8w@mail.gmail.com>
 <0ece40da-762a-4190-9cc8-23ff432fd441@bastelstu.be>
Message-ID: <69867F01.2070107@adviesenzo.nl>
Date: Sat, 7 Feb 2026 00:53:37 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:38.0) Gecko/20100101
 Thunderbird/38.7.0
Precedence: list
MIME-Version: 1.0
In-Reply-To: <0ece40da-762a-4190-9cc8-23ff432fd441@bastelstu.be>
Content-Type: multipart/alternative;
 boundary="------------040204080402010101090206"
From: php-internals_nospam@adviesenzo.nl (Juliette Reinders Folmer)

This is a multi-part message in MIME format.
--------------040204080402010101090206
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit

On 6-2-2026 20:59, Tim Düsterhus wrote:
> On 2/2/26 19:00, Mirco Babin wrote:
>> # RFC
>>
>> I've been asked to follow the RFC process. And I've been told that the
>> rejected PHP RFC Make constructors and destructors return void
>> ( https://wiki.php.net/rfc/make_ctor_ret_void ) rejects my proposal.
>> However, my proposal is explicitly about the "new" operator and not
>> about return types. It does, however, concern return values.
>
> Personally I find the fact that it's illegal to define a return type 
> on `__construct()` to be a pretty good indication that the constructor 
> is not meant to be able to return anything. As such I'm a little 
> surprised by the disagreement in that RFC, though it should be noted 
> that a majority was in favor (just not a 2/3's majority).
>

FYI/Just in case anyone already wants to forbid this - there is a sniff 
available which will flag both constructors as well as destructors with 
a return type and/or when the function returns something: 
Universal.CodeAnalysis.ConstructorDestructorReturn

Ref: 
https://github.com/PHPCSStandards/PHPCSExtra#universalcodeanalysisconstructordestructorreturn-wrench-books

--------------040204080402010101090206
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta content="text/html; charset=utf-8" http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">On 6-2-2026 20:59, Tim Düsterhus wrote:<br>
    </div>
    <blockquote
      cite="mid:0ece40da-762a-4190-9cc8-23ff432fd441@bastelstu.be"
      type="cite">On 2/2/26 19:00, Mirco Babin wrote:
      <br>
      <blockquote type="cite"># RFC
        <br>
        <br>
        I've been asked to follow the RFC process. And I've been told
        that the
        <br>
        rejected PHP RFC Make constructors and destructors return void
        <br>
        ( <a class="moz-txt-link-freetext" href="https://wiki.php.net/rfc/make_ctor_ret_void">https://wiki.php.net/rfc/make_ctor_ret_void</a> ) rejects my
        proposal.
        <br>
        However, my proposal is explicitly about the "new" operator and
        not
        <br>
        about return types. It does, however, concern return values.
        <br>
      </blockquote>
      <br>
      Personally I find the fact that it's illegal to define a return
      type on `__construct()` to be a pretty good indication that the
      constructor is not meant to be able to return anything. As such
      I'm a little surprised by the disagreement in that RFC, though it
      should be noted that a majority was in favor (just not a 2/3's
      majority).
      <br>
      <br>
    </blockquote>
    <br>
    FYI/Just in case anyone already wants to forbid this - there is a
    sniff available which will flag both constructors as well as
    destructors with a return type and/or when the function returns
    something: Universal.CodeAnalysis.ConstructorDestructorReturn<br>
    <br>
    Ref:
<a class="moz-txt-link-freetext" href="https://github.com/PHPCSStandards/PHPCSExtra#universalcodeanalysisconstructordestructorreturn-wrench-books">https://github.com/PHPCSStandards/PHPCSExtra#universalcodeanalysisconstructordestructorreturn-wrench-books</a><br>
  </body>
</html>

--------------040204080402010101090206--