Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:118967
MIME-Version: 1.0
References: <CAPyj-LDUD7PZ9Bcpmsc0B_WjdnOSBPhdwfJsseB6n8PesPbzhw@mail.gmail.com>
 <CADyq6sL8jZGdmvL0swvDkyF9raikmUtxf9m2spgCMyabkw1uxg@mail.gmail.com>
 <504f616c-05c1-45ef-991e-2b4c79f72d07@app.fastmail.com> <CADyq6sK6ophr75YQDTpCzfh_nztum_Yhk7hskfi8z_HTJ4ha-A@mail.gmail.com>
In-Reply-To: <CADyq6sK6ophr75YQDTpCzfh_nztum_Yhk7hskfi8z_HTJ4ha-A@mail.gmail.com>
Date: Fri, 4 Nov 2022 17:07:42 +0200
Message-ID: <CABAhh3HD3znrmuU1pRYB48V_HhmwguM=aidvXCWc6Xf7jpTxzA@mail.gmail.com>
To: Marco Pivetta <ocramius@gmail.com>
Cc: Larry Garfield <larry@garfieldtech.com>, php internals <internals@lists.php.net>
Content-Type: text/plain; charset="UTF-8"
Subject: Re: [PHP-DEV] [RFC][Dynamic class constant fetch]
From: someniatko@gmail.com (someniatko)

> What's convenient about `Foo::{$bar}` vs `constant(Foo::class . '::' .
> $bar)`? I'm a bit confused by this :|
>
> Is it the few keystrokes added?

Even if ignoring syntax / convenience bikeshedding, I find it a really
valuable addition to the language self-consistency. It's symmetrical
to the already existing syntax of dynamic property fetch and dynamic
method calls. One could argue that it's dynamic, too much magic and
bad, but then we should either deprecate those features, or if not,
have this symmetry. The Principle of Least Amusement and human pattern
recognition overall with thank you.