Do we want functions to act as properties, or merely omit parens for ufcs/chaining?

[Andrei Alexandrescu]

On 1/29/13 6:33 AM, eles wrote:
> On Tuesday, 29 January 2013 at 11:13:19 UTC, jerro wrote:
>> need to adopt the inferior C# approach.
>
> And there is another problem with the "superior" D approach: a typing
> mistake in the name of a property might let you not with one property
> that is r/w, but with two properties to which one is r/o and the other
> is w/o.
>
> More, those functions might be placed several screens far one from the
> other.

I agree this is an issue. I think it's good language design to avoid 
"long-distance influence" of one declaration against another.

This is a strong argument for keeping @property for write properties.


Andrei