Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:118056
MIME-Version: 1.0
References: <CAH19jWitAAqEdBrqX3ZjGnw+Nfd_8C=qzqPyxnOM13EtgZhBvA@mail.gmail.com>
 <029d3b2e-e8d3-41d0-acc9-7f7514651030@www.fastmail.com>
In-Reply-To: <029d3b2e-e8d3-41d0-acc9-7f7514651030@www.fastmail.com>
Date: Wed, 22 Jun 2022 18:31:16 +0200
Message-ID: <CAOWwgp=AP34r9krBELzneDvEz1-TT9sSe6qfkjGSs9PJC6Fb2A@mail.gmail.com>
To: php <php@stefan-marr.de>, shinji igarashi <sji@sj-i.dev>
Cc: php internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="0000000000006ed6dd05e20bdea0"
Subject: Re: [PHP-DEV] [RFC] [Under Discussion] Constants in traits
From: nicolas.grekas+php@gmail.com (Nicolas Grekas)

--0000000000006ed6dd05e20bdea0
Content-Type: text/plain; charset="UTF-8"

> >
> > I'd like to start a discussion on an RFC to allow defining constants in
> traits.
> > https://wiki.php.net/rfc/constants_in_traits
> >
> > I'm looking forward to your feedback, including corrections on English
> wordings.
> >
> > Thanks!
> >
> > --
> > Shinji Igarashi
>
> I am initially lukewarm.  One thing not addressed in the RFC that should
> be: Why were constants left out of traits previously, and what has changed
> to make them make sense to include now?  (I don't recall, honestly, so I
> have no strong feelings one way or the other yet.)
>

That!

I'm also wondering why the default value of a const (and a property) could
not be changed by the class importing the trait? This sometimes hits me and
the original RFC doesn't explain why this is needed.

I added Stefan Marr in the loop in case he still checks this email address
and would like to shed some light on those questions. WDYT Stefan?

And I'd also be happy to see an implementation of this before voting, to be
sure this is something that can be achieved without too many troubles. Do
you think this is possible?

Cheers,
Nicolas

--0000000000006ed6dd05e20bdea0--