Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:110650 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 12835 invoked from network); 18 Jun 2020 13:01:31 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 18 Jun 2020 13:01:31 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 4726E1804F6 for ; Thu, 18 Jun 2020 04:47:27 -0700 (PDT) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on php-smtp4.php.net X-Spam-Level: X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM,HTML_MESSAGE, RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H2,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.2 X-Spam-ASN: AS15169 209.85.128.0/17 X-Spam-Virus: No X-Envelope-From: Received: from mail-lf1-f53.google.com (mail-lf1-f53.google.com [209.85.167.53]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by php-smtp4.php.net (Postfix) with ESMTPS for ; Thu, 18 Jun 2020 04:47:26 -0700 (PDT) Received: by mail-lf1-f53.google.com with SMTP id c21so3286053lfb.3 for ; Thu, 18 Jun 2020 04:47:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=BiU3YkbSUo+Pmyoizbj0p9FiBW0UQYgcFbNbEiUXCBM=; b=oTo6p1XBh2kSvIkAQQE+nQPfZ5468S/2kG4rD9mVePREfaF5tlkhGKEf/KlQv4wsIz WE5HjSLiOvPhZKOaylSxZrtgr4w184quk/pRbxat7eohnXindMDQMPHXqSG3WAFFOpgi /E5DgJ2ApSUi8HZVBcwkMlTz+Oot+C3BdOz4pIhoCOqXIzF7v/0b7cP5Z7q0Gp6/mvs7 6rf4mw/LZWLkEcgrFLji+ysbVnZN99xE39knHWJzsY+fJFjSYc2tpTh5/FaXeJdd1qK7 d1nff6KqAGKcLgOCcbY9NPbyiTIO2xMhzGeegQi3CFbwO71sId0JGIhpIOyebLKDW87v CJzw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=BiU3YkbSUo+Pmyoizbj0p9FiBW0UQYgcFbNbEiUXCBM=; b=jfhB9EErmpxp8QpDMfVcTs8icYsJKsdFqnZoqaJJRJz67f+Cdzactlw2TesfD51Cxk OVVz73FfcViNMDqiqkrcwMmhFcWsK7y6UY5NLxOem3JQ/YN+q+eSUycrUwRSJgfHUhnG WgMU9ZKFv9QUBPAVpR3TB6fBZmkvWkPh4KIetiojfaKrbQ6ABU3vhB9l6qUjJTe9tkzh cStKUCE+7XKr2ojTVL1XFkmb8TF5B/Acqq9FkhcjHFbadt8FfJoqZXIB4AIoXzGLxI8f W4I/ETkYKibfZZ9O13UydA5XB80ItfBU7Xcc+fMSkxiW6hHzWj6kFm4gZfN8f5Q4Pt6O 7wrg== X-Gm-Message-State: AOAM532zcvrFSBkn0PYq3+cR+xn9X/vFQnszpHvOLK8E23q3IyoXFLB3 gYGx2p6b1pfMFBKxIPK28VMHsZdGGj6yoYBIBU7DxD2/ X-Google-Smtp-Source: ABdhPJyrpRIgaXKLqdzaocL2rGdYg5Fw5qvO4jb7kusZcPAeU7srWCtkso0dFJSMKnO8+YWp47wGlNPY3sZybkQlvwY= X-Received: by 2002:a19:3f01:: with SMTP id m1mr2152591lfa.130.1592480843051; Thu, 18 Jun 2020 04:47:23 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: Date: Thu, 18 Jun 2020 14:47:09 +0300 Message-ID: To: PHP Internals List Content-Type: multipart/alternative; boundary="000000000000f637f305a85a5686" Subject: Re: [RFC] [DISCUSSION] Make constructors and destructors return void From: benas.molis.iml@gmail.com (Benas IML) --000000000000f637f305a85a5686 Content-Type: text/plain; charset="UTF-8" Hey internals, 1. Since there is confusion around multiple RFCs, I would like to emphasize that this RFC (Make constructors and destructors return void) superseded the original RFC (Allow void return type on constructors/destructors). Thus, the latter RFC is now abandoned. Link to the new RFC: https://wiki.php.net/rfc/make_ctor_ret_void Link to the old RFC: https://wiki.php.net/rfc/constructor_return_type I would also like to inform you that the new RFC is now complete. As such, I have put the RFC into "Under Discussion" status. 2. Since this RFC is proposing a rather small BC break (given that there will be a deprecation warning in PHP 8.0), should we start enforcing `void` rules on constructors and destructors in PHP 8.1 or PHP 9.0? Best regards, Benas On Wed, Jun 17, 2020, 2:10 AM Benas IML wrote: > Hey internals, > > This is a completely refined, follow-up RFC to my original RFC. Based on > the > feedback I have received, this PR implements full validation and implicitly > enforces `void` rules on constructors/destructors while also allowing to > declare an **optional** explicit `void` return type. Note, that there is a > small but justifiable BC break (as stated by the RFC). > > RFC: https://wiki.php.net/rfc/make_ctor_ret_void > > Best regards, > Benas Seliuginas > --000000000000f637f305a85a5686--