Re: [IDEA for RFC] let the "new" operator fail when the __construct() function returns a value.
| From: | Mirco Babin | Date: | Sat, 14 Feb 2026 14:00:48 +0000 |
| Subject: | Re: [IDEA for RFC] let the "new" operator fail when the __construct() function returns a value. | ||
| References: | 1 2 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-130076@lists.php.net to get a copy of this message | ||
Hello Tim Düsterhus,
>… the time investment would equally apply to anyone else writing an RFC
>on your behalf. In fact it would possibly be even larger, since they
>would have to become familiar with the issue first, whereas you already
>encountered in practice, so you already have an idea of what needs to
>change and *just* need to write it down.
This argument has convinced me. And writing it down helps clear my mind.
>All that said: If you are willing prepare an initial RFC Draft based on
>the official RFC template (https://wiki.php.net/rfc/template) and to go
>through the process of officially discussion the RFC, I'm happy to do
>the “polishing” work as an official coauthor / mentor to make sure there
>are no missing bits or other mistakes. I'm also willing to get someone
>to do the implementation (potentially I'm doing it myself).
>
>Do we have a deal? :-)
I have prepared a RFC at
https://gist.github.com/MircoBabin/aaa574297c8d1baa879f19c99ce28e93
Are you still willing to carry out the implementation? If so:
- Should I mention you as coauthor?
- In the first chapter, what wording should "Implementation" be?
- What wording should "Patches and Tests" be?
Kind regards,
Mirco Babin