Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:107108
Content-Type: text/plain;
	charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
In-Reply-To: <CABdc3Wpit02=BqvVE85ciw9qo3UYc2LBatOy23yFk5z+quZ2rw@mail.gmail.com>
Date: Sun, 15 Sep 2019 08:48:45 -0500
Cc: PHP Internals List <internals@lists.php.net>
Content-Transfer-Encoding: quoted-printable
Message-ID: <18D5453E-D962-467C-A50C-52658C11BB25@pmjones.io>
References: <CABdc3Wpit02=BqvVE85ciw9qo3UYc2LBatOy23yFk5z+quZ2rw@mail.gmail.com>
To: =?utf-8?Q?Micha=C5=82_Brzuchalski?= <michal.brzuchalski@gmail.com>
Subject: Re: [PHP-DEV] [RFC] Object Initializer
From: pmjones@pmjones.io ("Paul M. Jones")



> On Sep 12, 2019, at 09:00, Micha=C5=82 Brzuchalski =
<michal.brzuchalski@gmail.com> wrote:
>=20
> Hi internals,
>=20
> I'd like to open discussion about RFC: Object Initializer.
>=20
> This proposal reduces boilerplate of object instantiation and =
properties
> initialization in case of classes without required constructor =
arguments as
> a single expression with initializer block.
>=20
> https://wiki.php.net/rfc/object-initializer

This reminds me of how Hack/HHVM would initialize object properties from =
constructor parameters; I remember finding it very appealing.

IIRC, you would provide the property signature as a constructor =
parameter to trigger the initialization:

```php
class Foo
{
    protected int $bar;

    public function __construct(protected int $bar)
    {
    }

    public function getBar() : int
    {
        return $this->bar;
    }
}

$foo =3D new Foo(1);
echo $foo->getBar(); // 1
```

Perhaps something like that is worth adopting here.



--=20
Paul M. Jones
pmjones@pmjones.io
http://paul-m-jones.com

Modernizing Legacy Applications in PHP
https://leanpub.com/mlaphp

Solving the N+1 Problem in PHP
https://leanpub.com/sn1php