Re: [RFC] Property accessors

From: Date: Tue, 04 May 2021 15:22:06 +0000
Subject: Re: [RFC] Property accessors
References: 1  Groups: php.internals 
Request: Send a blank email to internals+get-114272@lists.php.net to get a copy of this message
2021-05-04 12:33 GMT+02:00, Nikita Popov <nikita.ppv@gmail.com>:
> Hi internals,
>
> I'd like to present an RFC for property accessors:
> https://wiki.php.net/rfc/property_accessors
>
> Property accessors are like __get() and __set(), but for a single property.
> They also support read-only properties and properties with asymmetric
> visibility (public read, private write) as a side-effect.
>
> The proposal is modeled after C#-style accessors (also used by Swift), and
> syntactically similar to the previous
> https://wiki.php.net/rfc/propertygetsetsyntax-v1.2
> proposal.
>
> While I put a lot of effort into both the proposal and the implementation,
> I've grown increasingly uncertain that this is the right direction for us
> to take. The proposal turned out to be significantly more complex than I
> originally anticipated (despite reducing the scope to only "get" and "set"
> accessors), and I'm sure there are some interactions I still haven't
> accounted for. I'm not convinced the value justifies the complexity.
>
> So, while I'm putting this up for discussion, it may be that I will not
> pursue landing it. I think a lot of the practical value of this accessors
> proposal would be captured by support for read-only (and/or private-write)
> properties. This has been discussed (and declined) in the past, but
> probably should be revisited.
>
> Regards,
> Nikita
>

Is this a typo?

get() {}       // Must not have parameter list

But there are no parameters...?

Olle


Thread (18 messages)

« previous php.internals (#114272) next »