> The original motivation was, IIRC, to initialize class constants with an
> expression.
> Following KISS, I feel we should constrain our efforts to that scope, and
> that's how I voted:
> "Yes" on class constants and static members, "No" on everything else.
I'd also personally found the
> On Feb 19, 2020, at 2:00 PM, Bishop Bettini wrote:
>
> Consequently, the only way to safely initialize class constants and static
> members is at run-time, and I can only think of one way to do it. Apologies
> if this has already been suggested: taking a cue from C#, a static class
>
On Wed, Feb 19, 2020 at 12:58 PM tyson andre
wrote:
> Hi internals,
>
> > I've created a straw poll at
> https://wiki.php.net/rfc/calls_in_constant_expressions_poll , to measure
> interest in allowing calls in different types of constant expressions.
> > If there aren't any problems with the
Hi internals,
> I've created a straw poll at
> https://wiki.php.net/rfc/calls_in_constant_expressions_poll , to measure
> interest in allowing calls in different types of constant expressions.
> If there aren't any problems with the poll structure or rules preventing
> creating a poll, I was
> > I've created a straw poll at
> > https://wiki.php.net/rfc/calls_in_constant_expressions_poll ,
> > to measure interest in allowing calls in different types of constant
> > expressions.
>
> I've yet to make my mind up for most circumstances, although I'm leaning
towards a general "No".
>
>
On 17/02/2020 02:08, tyson andre wrote:
I've created a straw poll at
https://wiki.php.net/rfc/calls_in_constant_expressions_poll , to measure
interest in allowing calls in different types of constant expressions.
I've yet to make my mind up for most circumstances, although I'm leaning
towards
