> On Feb 21, 2020, at 5:20 PM, Rowan Tommins wrote:
>
> On 20 February 2020 14:13:58 GMT+00:00, Nikita Popov
> wrote:
>> Hi internals,
>>
>> I'd like to start the discussion on the "explicit call-site
>> pass-by-reference" RFC again:
>> https://wiki.php.net/rfc/explicit_send_by_ref
>
> My
When writing immutable classes, I want to be able to set properties in
static factories and in wither methods.
Once the new instance is sent to the outside world, its properties can be
locked to prevent further modification.
This sounds to me like we need different modes. Either the object
On Fri, Feb 21, 2020, at 4:29 AM, Máté Kocsis wrote:
> >
> > Yeah, I'm definitely thinking in relation to the earlier discussion, since
> > I think they're all inter-related. (This, property accessors, and constant
> > expressions.)
> >
>
> The biggest question is whether it's worth to support
On 20 February 2020 14:13:58 GMT+00:00, Nikita Popov
wrote:
>Hi internals,
>
>I'd like to start the discussion on the "explicit call-site
>pass-by-reference" RFC again:
>https://wiki.php.net/rfc/explicit_send_by_ref
Hi Nikita,
Thanks for putting the case for this so clearly. My instinctive
>
> Of course, that does leave the question of how often you need one or the
> other. Maybe just the asymmetric visibility is sufficient for most
> practical purposes, in which case it may not be worthwhile to introduce
> readonly properties as a separate feature.
>
The examples shown in my
>
> Yeah, I'm definitely thinking in relation to the earlier discussion, since
> I think they're all inter-related. (This, property accessors, and constant
> expressions.)
>
The biggest question is whether it's worth to support both readonly
properties and property accessors. My answer is clear
On Thu, Feb 20, 2020 at 10:12 AM Nikita Popov wrote:
> FWIW, it is our established stance that all error messages must be
> capitalized. Lower-case first character is only permitted if it is part of
> a function name, or similar cases.
>
Thanks for clearing this up, Nikita.
Given that, I think
On Fri, Feb 21, 2020 at 12:05 AM Larry Garfield
wrote:
> On Thu, Feb 20, 2020, at 8:47 AM, Levi Morrison via internals wrote:
> > Just chiming in to voice strong support for this RFC. This is a key
> > piece toward making PHP code statically analyzable. If it becomes
> > required at the call
