Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:114510
To: "internals@lists.php.net" <internals@lists.php.net>
Thread-Topic: [PHP-DEV] [RFC]: Allow static properties in enums
Thread-Index: AQHXSyQDVDy99aZ9kUmonoEBFwdfBarnuCqAgAADjgCAABjeAIAAjcbT
Date: Tue, 18 May 2021 00:46:40 +0000
Message-ID:
 <DM6PR07MB6618C7446A771452DEB9D5DCF92C9@DM6PR07MB6618.namprd07.prod.outlook.com>
References:
 <DM6PR07MB6618AA302ABC6DC7A37B609BF92D9@DM6PR07MB6618.namprd07.prod.outlook.com>
 <CABdc3WpFk9qf10D=fEscB6LynmdN2_yFHW1b_Mz1m837=YOhTg@mail.gmail.com>
 <a8cca9f4-10c2-47ee-a6f9-c27e247d4734@www.fastmail.com>,<CABdc3WrYW9HQZ1D8F001HNCrY-UmFO2Z_+owMAYJk=mxzKjWTA@mail.gmail.com>
In-Reply-To:
 <CABdc3WrYW9HQZ1D8F001HNCrY-UmFO2Z_+owMAYJk=mxzKjWTA@mail.gmail.com>
Accept-Language: en-CA, en-US
Content-Language: en-CA
x-ms-exchange-messagesentrepresentingtype: 1
x-tmn: [3QdjjWjY1TNFu04+Sg3U653VEjr+CIIl/G27skHUPKWNGCq/DCl5aZiYA3XqXI80]
x-ms-publictraffictype: Email
x-incomingheadercount: 44
x-eopattributedmessage: 0
x-ms-office365-filtering-correlation-id: 78551cc4-c935-4cc2-30a9-08d9199666d2
x-ms-traffictypediagnostic: DM6NAM12HT127:
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info:
 qJLElhne5+6bjjBdvuLzbpUHm0fKWpE5bu4vJeWOmTsfMWpOtAvz8JWaoJAAAE/7e6dy+3T8g+W2FgJXExlhQ5NsuvRaY27acHqJLTMiNDwo75/5bedqscXZXgW9r9/PZRLNivr1vVm2PeoVjNLEi2VpfOHULtCyThxk74jBIqRFDSYN9pK3wY20ueIN12CFk6fo4DAhhIgTKOCkkYmAGlpNLkhlOW1zcAuAEQrn2FIjctHSJnsjmbB+ieth5SPC6v+EsRew+K2vFGx/n59+Spjvab+XxleXxD9iHlc1RfRU7OSH/vuEqlo3rkUnk2G55MtyHNu3bkiGxmqonwZi4kRzy8Q24PmNJEmhiAWrVKauJMcsL2bQEoMjJ1/R/7WFE92WH0Bue2hfBe5vGOlfsb8y6VYF5CaoB874Fzo/Hu3AVvyVkChiwxO9QnrIiulRZOYcc4mHcrYvC5T+a8HQfA==
x-ms-exchange-antispam-messagedata:
 WKEetvm9hpnPaM62BVu6SeMmYoLaE+FMXWpYVWIvqHCsZadR+etBShGV6+OmjqvMC77sJ1LCh2QpAuJuo+EioQ/XJdtPfh0hLFcoxfau66jsL/N5hGho5Qq9V7WvTH+SJIEZ9JKZG+jMDLL9UP8Ay1rPoPY0xoeJh4I6VTgroxeJwCj1OxSWV+mCwY7eHiKN2x4UdQ4XSI73PCxI0Xmigw==
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="iso-8859-2"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: hotmail.com
X-MS-Exchange-CrossTenant-AuthAs: Anonymous
X-MS-Exchange-CrossTenant-AuthSource: DM6NAM12FT004.eop-nam12.prod.protection.outlook.com
X-MS-Exchange-CrossTenant-RMS-PersistedConsumerOrg: 00000000-0000-0000-0000-000000000000
X-MS-Exchange-CrossTenant-Network-Message-Id: 78551cc4-c935-4cc2-30a9-08d9199666d2
X-MS-Exchange-CrossTenant-originalarrivaltime: 18 May 2021 00:46:40.9696
 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Internet
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: DM6NAM12HT127
Subject: Re: [PHP-DEV] [RFC]: Allow static properties in enums
From: tysonandre775@hotmail.com (tyson andre)

> > On Mon, May 17, 2021, at 9:16 AM, Micha=B3 Marcin Brzuchalski wrote:=0A=
> > > pon., 17 maj 2021, 16:02 u=BFytkownik tyson andre <=0A=
> > tysonandre775@hotmail.com>=0A=
> > > napisa=B3:=0A=
> > >=0A=
> > > > Hi internals,=0A=
> > > >=0A=
> > > > I've created a new RFC=0A=
> > > > https://wiki.php.net/rfc/enum_allow_static_properties=0A=
> > > >=0A=
> > > > Although enums are immutable objects, it is often useful to have=0A=
> > functions=0A=
> > > > or methods that operate on enum instances.=0A=
> > > > In many cases, it would make sense to declare that functionality as=
=0A=
> > static=0A=
> > > > methods on the enum itself.=0A=
> > > > In cases where static methods require shared state, it would be use=
ful=0A=
> > to=0A=
> > > > allow storing those shared state in static properties.=0A=
> > > > To ensure immutability of enum instances, it's only necessary to fo=
rbid=0A=
> > > > instance properties, but all properties were forbidden in the initi=
al=0A=
> > > > functionality included with the enums RFC.=0A=
> > > >=0A=
> > > > This RFC proposes allowing static properties in enums, while=0A=
> > continuing to=0A=
> > > > forbid instance properties.=0A=
> > > >=0A=
> > >=0A=
> > > Would you be able to provide more real life example?=0A=
> > > The example in RFC could easily encapsulate current Environment readi=
ng=0A=
> > in=0A=
> > > for eg. EnvironmentConfiguration class with static property and metho=
d=0A=
> > and=0A=
> > > TBH possibly that would be my preference to solve this.=0A=
> >=0A=
> > I would agree.=A0 Static properties are ugly to begin with.=A0 They're =
globals=0A=
> > with extra syntax.=A0 I have no desire to see them on enums.=0A=
> >=0A=
> > Also a clarification, since it wasn't entirely clear in Tyson's origina=
l=0A=
> > email: Static methods on Enums *are already supported*.=A0 They were in=
cluded=0A=
> > in the original Enum RFC.=A0 The change proposed here is just about sta=
tic=0A=
> > properties.=0A=
> >=0A=
> =0A=
> Personally, I'd prefer to see enums as value objects only, adding static=
=0A=
> properties allow to implementation of statically conditional behaviour.=
=0A=
> IMO enums should consist only of pure functions. This is why I'd vote NO =
on=0A=
> this proposal.=0A=
> =0A=
> Cheers,=0A=
> Micha=B3 Marcin Brzuchalski=0A=
=0A=
Hi internals,=0A=
=0A=
I've updated https://wiki.php.net/rfc/enum_allow_static_properties to inclu=
de the arguments made so far against/for including=0A=
static properties, as well as including more arguments/examples in favor of=
 including static properties in traits.=0A=
=0A=
Thanks,=0A=
- Tyson=0A=