Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:118092
MIME-Version: 1.0
References: <CAPyj-LBQmoFEGZyMw3H5fAy-NwP3WdkH2ZviHWcBrhJ_8qrOGg@mail.gmail.com>
 <bb40be07-c3fc-4ca9-9365-37a50b8339cd@www.fastmail.com>
In-Reply-To: <bb40be07-c3fc-4ca9-9365-37a50b8339cd@www.fastmail.com>
Date: Fri, 24 Jun 2022 18:43:32 +0200
Message-ID: <CAOWwgpmQC8ptMCn7JwV31nAzA3v76ERxM-XDi-+RQnfezAO1=g@mail.gmail.com>
To: Larry Garfield <larry@garfieldtech.com>, Benjamin Eberlei <kontakt@beberlei.de>
Cc: php internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000fff50605e234454b"
Subject: Re: [PHP-DEV] [RFC][Under discussion] Fetch properties in const expressions
From: nicolas.grekas+php@gmail.com (Nicolas Grekas)

--000000000000fff50605e234454b
Content-Type: text/plain; charset="UTF-8"

> > Hi everyone
> >
> > I'd like to start a discussion on a simple RFC to allow fetching
> > properties in constant expressions.
> > https://wiki.php.net/rfc/fetch_property_in_const_expressions
> >
> > The RFC proposes adding support for fetching properties in constant
> > expressions using the -> operator. I'm looking forward to your
> > feedback.
> >
> > Regards,
> > Ilija
>
> The enum-in-attribute use case came up recently in Symfony.  I'm in favor
> and the RFC looks good to me.
>

Genuine question:

In the thread about auto-implementing Stringable for string backed enums,
there is extensive argumentation to explain why ppl that use enums this way
are wrong. You mentioned writing a blog post about these reasons Larry, and
Benjamin (/cc) also expressed a similar opinion.

So my question is: don't these arguments apply here also? Shouldn't we
reject this RFC and tell ppl to use consts instead? If not, why?

Nicolas

--000000000000fff50605e234454b--