Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:116160
To: "internals@lists.php.net" <internals@lists.php.net>
Thread-Topic: [PHP-DEV] Allowing `(object)['key' => 'value']` in initializers?
Thread-Index: AQHXsiErO0Vz7k4CHEy3AX0ZJcoPi6u05TYAgAACQZ4=
Date: Sat, 25 Sep 2021 16:00:00 +0000
Message-ID:
 <DM5PR17MB14817688E62B37B1A19DB7E2F9A59@DM5PR17MB1481.namprd17.prod.outlook.com>
References:
 <DM5PR17MB14811B9276E2BC5ADFA347D2F9A59@DM5PR17MB1481.namprd17.prod.outlook.com>
 <CADyq6sKZxP=ihPRV6=PzORMVUGzENDaWa_vOpVb85Fc6+PUvgA@mail.gmail.com>
In-Reply-To:
 <CADyq6sKZxP=ihPRV6=PzORMVUGzENDaWa_vOpVb85Fc6+PUvgA@mail.gmail.com>
Accept-Language: en-CA, en-US
Content-Language: en-CA
suggested_attachment_session_id: 1ac4474b-9dcc-9296-8b5b-d21dcf66342b
x-ms-exchange-messagesentrepresentingtype: 1
x-tmn:
 [93Su6DAPcDL5CEA+o1WGSN9yYeqNAzkdMStHD6bcgduV8CRsv2gqtwTXN7RaW5LKRqbPbntxAfg=]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 1c14d447-3a1d-44c6-ed19-08d9803d8767
x-ms-traffictypediagnostic: DM6PR17MB3163:
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info:
 ayCPiJSmXyWEb+WdPd5h2VHJUusU9376VLFC9sWMiP9oKa7J3qJcXi/ktWCYUjJdOlkY7VEcpi12mGfKM5NRN7eLQfQ00RaIJIjXNlQkZxMMhFl3EMfh0bhfa9RssksO7+Igdr1YToOETbclaERIkPXTFoYaEbzDkTBJVEIC3qwmB3iZkgHBTUvgnUugOrkzXYysTiqxPr4HnIU0decZV6aw1Q5NzyBAkMoaWOtED2Ss/bQtyMjGCs/OuqX5nW1GPEglK1EQyJRHweCb3z6c10lzKODXf36e9xbXJ4wGCsHjUxP2II/CuRkaSyBcFey5rBYyqVJgZZf8fyvW1S67rYwtrudFOHbzXZb0vCVDUupPw524LL0/7dEfVky62ss9NaRPkYkXdmWg/a/vuzMeeb7x+ySLzWLiKlL2kUovr632JuZ8Tb1ie1ucpzdvoIB7SYQMiwyOiYnJCv20n+uyE39x6lbQh70SqhQHgsRBaC4whqeMshHJSXYl6CASws8e1ocuaEMScNPGBzA5a/QA6A==
x-ms-exchange-antispam-messagedata-chunkcount: 1
x-ms-exchange-antispam-messagedata-0:
 6irzNzUcJvbrL4pTNi6fd/d48HsZaIAisQFtdaUlis7Kb9ZuUNJFSZbqABDc5gi83FMFUYzwK1QgXBtoAQeDP3ekx00GnaEVrK27VoBh+1kpdRf359JzX9vZoJ9+9KEhFMWSANB3k713JaNgLWMV3gPa1NcVHWsRQb5bigIvpDqciTDI0PhWgDcQFYHFp4eJklKmXIgLqIvnmd+CW/9p0A==
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: sct-15-20-3174-20-msonline-outlook-21df5.templateTenant
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: DM5PR17MB1481.namprd17.prod.outlook.com
X-MS-Exchange-CrossTenant-RMS-PersistedConsumerOrg: 00000000-0000-0000-0000-000000000000
X-MS-Exchange-CrossTenant-Network-Message-Id: 1c14d447-3a1d-44c6-ed19-08d9803d8767
X-MS-Exchange-CrossTenant-originalarrivaltime: 25 Sep 2021 16:00:00.2091
 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa
X-MS-Exchange-CrossTenant-rms-persistedconsumerorg: 00000000-0000-0000-0000-000000000000
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM6PR17MB3163
Subject: Re: [PHP-DEV] Allowing `(object)['key' => 'value']` in initializers?
From: tysonandre775@hotmail.com (tyson andre)

Hey Marco Pivetta,=0A=
=0A=
> > What are your thoughts on allowing the `(object)` cast in initializer t=
ypes where `new` was already allowed, but only when followed by an array li=
teral node. (e.g. continue to forbid `(object)SOME_CONSTANT`) (see https://=
wiki.php.net/rfc/new_in_initializers)=0A=
> > ...=0A=
> > Reasons:=0A=
> > - The ability to construct empty stdClass instances but not non-empty o=
nes is something users would find surprising,=0A=
> >   and a lack of support for `(object)[]` be even more inconsistent if f=
actory methods were allowed in the future.=0A=
> > - stdClass is useful for some developers, e.g. in unit tests, when usin=
g libraries requiring it for parameters,=0A=
> >   when you need to ensure data is encoded as a JSON `{}` rather than `[=
]`, etc.=0A=
> > - It would help developers write a clearer api contract for methods,=0A=
> >   e.g. `function setData(stdClass $default =3D (object)['key' =3D> 'val=
ue'])`=0A=
> >   is clearer than `function setData(?stdClass $default =3D null) { $def=
ault ??=3D (object)['key' =3D> 'value']; `=0A=
> > - stdClass may be the only efficient built-in way to represent objects =
with arbitrary names if RFCs such as https://externals.io/message/115800 pa=
ssed=0A=
=0A=
> =A0 passed=0A=
>=0A=
> Right now, there's even an interest in getting rid (or deprecating) dynam=
ic properties on objects: why push the complete opposite ways?=0A=
> =0A=
> What is the actual value of using an stdClass instance instead of an `arr=
ay<string, mixed>` (already supported)?=0A=
=0A=
My original message had a section with reasons why an end user might want t=
hat.=0A=
=0A=
There's a push for getting rid of (or deprecating) dynamic properties on **=
objects that are not stdClass (or subclasses)**=0A=
Not a push for getting rid of stdClass. Way too many things use stdClass to=
 get rid of stdClass.=0A=
(whether or not stdClass gets aliased or even renamed to DynamicObject).=0A=
=0A=
```=0A=
php > var_dump(json_decode('{}'));=0A=
object(stdClass)#1 (0) {=0A=
}=0A=
```=0A=
=0A=
Thanks,=0A=
Tyson=