On Wed, Jul 8, 2020 at 10:15 PM Benas IML <benas.molis....@gmail.com> wrote:
> Hey internals, > > I have reopened the voting. It is going to close July 22nd, 2020. I have > also > added a "Why allow void return type on constructors/destructors?" section > which > I hope internals are going to read and consider before voting. Thanks! > I wanted to give a datapoint for my no vote. I think going from forbidding return types on ctors to requiring them to be void is one step to far. Yes, the use-cases for returning something from a constructor are questionable, but why force something that strictly is not something the language should care about, as it can as easily be a coding style topic. For me the RFC vote should be "allow to dcelare return types on constructors/destructors?", then people *can* declare void, but *can* also declare other things, but nothing *must* be done. Then it becomes a question of coding styles enforcing "void" for all constructors of a project for example. I would vote Yes on that. > RFC: > https://wiki.php.net/rfc/make_ctor_ret_void > > Best regards, > Benas > > On Fri, 3 Jul 2020 at 00:12, Benas IML <benas.molis....@gmail.com> wrote: > > > > Hey internals, > > > > I have opened the voting for the RFC, let's hope everything is going > > to be smooth :). If you have any other questions, let me know! > > > > RFC: https://wiki.php.net/rfc/make_ctor_ret_void > > > > Best regards, > > Benas Seliuginas > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: https://www.php.net/unsub.php > >
