Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:107046
Message-ID: <DC7DE0EB-89E0-4AD3-BF18-382E35F976FE@newclarity.net>
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_B5B02C4A-111E-485F-90EE-83DB5B31C769"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Date: Fri, 13 Sep 2019 00:22:36 -0700
In-Reply-To: <CANS-=peR=rcZeHcRvZFxJPDsA402MKv_BxZ=ftU=Zo8Nad4CdQ@mail.gmail.com>
Cc: =?utf-8?Q?Micha=C5=82_Brzuchalski?= <michal.brzuchalski@gmail.com>,
 PHP Internals List <internals@lists.php.net>
To: Lynn <kjarli@gmail.com>
References: <CABdc3Wpit02=BqvVE85ciw9qo3UYc2LBatOy23yFk5z+quZ2rw@mail.gmail.com>
 <CANS-=peR=rcZeHcRvZFxJPDsA402MKv_BxZ=ftU=Zo8Nad4CdQ@mail.gmail.com>
Subject: Re: [PHP-DEV] [RFC] Object Initializer
From: mike@newclarity.net (Mike Schinkel)

--Apple-Mail=_B5B02C4A-111E-485F-90EE-83DB5B31C769
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

> What's the added benefit of this compared to implementing a =
constructor?

Michal my have a different answer but my answer are the following two =
benefits plus a 3rd related benefit:

1. The ability to add strictness to object initialization vs. using =
arrays of properties.  PHP itself could flag misspelled or missing =
properties with a warning or an error which is something PHP cannot =
really do given that array keys are strings and not identifiers.

2. The ability for tools like PhpStorm, PHStan and others to more easily =
identify and flag these errors. It is hard (impossible?) for a tool to =
validate array element keys because there is no way to declare named and =
typed array elements keys in PHP.

3. It would empowering developers to pass optional elements to functions =
and methods that can also be type checked. The 2nd example would allow =
type checking but the first would not:


EXAMPLE 1
function foo( int $id, array $args ) {
	...
}
foo( 1, array(
	"bar" =3D> "abc",
	"baz" =3D> 123,
}


EXAMPLE 2
class FooArgs {
	public string $bar
	public int $baz
}
function foo( int $id, FooArgs $args ) {
	...
}
foo( 1, FooArgs{
	bar =3D "abc",
	baz =3D 123,
}



-Mike


> The part I like is that this can be used to replace =
stdClass/structured
> arrays. Perhaps something like this would nice to have in PHP:
>=20
> ```
> $people =3D [];
>=20
> foreach ($peopleFromDatabase as [$id, $username, $name]) {
>    $people[] =3D {
>        Uuid id =3D> $id,
>        string username =3D> $username,
>        string name =3D> $name,
>    };
>    // and possible automatic assignment:
>    $people[] =3D {Uuid $id, string $username, string $name};
> }
> ```
>=20
> Regards,
> Lynn van der Berg


--Apple-Mail=_B5B02C4A-111E-485F-90EE-83DB5B31C769--