@property fields

Dom DiSc dominikus at scherkl.de
Wed Dec 4 11:12:27 UTC 2024


On Tuesday, 3 December 2024 at 23:50:20 UTC, Richard (Rikki) 
Andrew Cattermole wrote:
> The ``@property`` attribute has been left in the lurch for 
> quite some time, where only one behaviour related to its return 
> value being of any value.
>
> There are two parts of this proposal, however I am only 
> confident in the first part, fields.

Why do we need @property fields?
I mean, it's nice tho have the setter and getter beeing created 
automatically, but one of the important properties of @property 
is to have control if you want only a getter (read only) or only 
a setter (write only), but here you get always both.

Also, I mainly use @property if I do NOT have a field, but the 
value is generated on the fly from other data (getter) or the 
input produces other effects/change multiple fields (setter).


More information about the dip.ideas mailing list