Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:120110
MIME-Version: 1.0
References: <CACtG6sCFbMniVPwkib5FE6Oi=+-mEWT+tQuWuAZdyjQX3vR0Hw@mail.gmail.com>
 <fd3e3d53-e7f1-5db1-ee06-f4dd8ce5b5b4@gmail.com> <CABJDihuki8mdKM5XMqMN8UseY-p=dO4RgVMbNPUxnAEMxoO8Cg@mail.gmail.com>
In-Reply-To: <CABJDihuki8mdKM5XMqMN8UseY-p=dO4RgVMbNPUxnAEMxoO8Cg@mail.gmail.com>
Date: Sun, 23 Apr 2023 18:01:16 +0200
Message-ID: <CAPzBOBMB4RCTVvDKpHvo-3A2iixR01TbjuY1vMjhQCo==dq8+w@mail.gmail.com>
To: Lokrain <lokrain@gmail.com>
Cc: Niels Dossche <dossche.niels@gmail.com>, Garet Claborn <garet@suiteux.com>, internals@lists.php.net
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] Introduction - SuitespaceRnD
From: landers.robert@gmail.com (Robert Landers)

On Sun, Apr 23, 2023 at 1:57=E2=80=AFPM Lokrain <lokrain@gmail.com> wrote:
>
> Hello,
>
> For me, this is just a wrong way of using enums for the sake of opinionat=
ed
> solution of specific problem.
>
> Regards,
> Dimitar
>
> On Sun, 23 Apr 2023 at 14:23, Niels Dossche <dossche.niels@gmail.com> wro=
te:
>
> > Hi
> >
> > On 4/19/23 17:11, Garet Claborn wrote:
> > > Hello PHP Internals,
> > >
> > > I am Garet Claborn, CTO for Suitespace Inc
> > > <https://www.getsuiteux.com/>, leading
> > > up our R&D team. Just registered and my PHP Wiki username is:
> > > *suitespacernd*
> > >
> > > We use PHP extensively in our projects. Specifically I finally regist=
ered
> > > as I have written up an RFC in response to this issue thread
> > > <https://github.com/php/php-src/issues/9208> on GitHub. While I am
> > notably
> > > attached to said issue, I hope to provide useful feedback in general =
from
> > > our case studies.
> > >
> > > Feel free to reach out for whatever reason.
> > >
> > > Cheers,
> > > Garet Claborn
> > >
> > > CTO, Suitespace Inc
> > > garet@suiteux.com
> > >
> >
> > Good luck with the RFC, I'm also quite interested in this feature so I'=
m
> > interested to see where it goes.
> > You might also want to explicitly ask for RFC karma so that you can cre=
ate
> > a wiki page for the RFC, if you haven't done that already :)
> >
> > Kind regards
> > Niels
> >
> > --
> > PHP Internals - PHP Runtime Development Mailing List
> > To unsubscribe, visit: https://www.php.net/unsub.php
> >
> >

> For me, this is just a wrong way of using enums for the sake of opinionat=
ed
> solution of specific problem.

That seems a bit of a strong reaction, though I agree that this can be
solved fairly easily in user-land:

trait ArrayKey {
  public function key(): string {
    return get_class($this) . '::' . $this->name;
  }
}
enum T { use ArrayKey; case A; case B; }
echo T::A->key();
// outputs: T::A

or even set it up in the constructor.

If you don't have control over the enums, you can write a simple
function to the same. As a side-note, I would rather have enums able
to be casted to a string than to change how arrays work. Even if it
has to be something 'ugly' to keep people from using that itself as a
value (similar to how js symbol types work -- a one-way cast).