@property - take it behind the woodshed and shoot it?

[Jonathan M Davis]

On Thursday, January 24, 2013 21:24:05 Andrei Alexandrescu wrote:
> On 1/24/13 9:11 PM, Jonathan M Davis wrote:
> > I believe that that's what we have now. The problem is when you want a
> > property which returns a delegate. And for that, we need @property.
> > Getting
> > rid of @property makes it a problem, whereas with @property, it can work -
> > as can property functions which return delegates.
> 
> Well how about we just renounce those for the sake of simplification.

Without explicit properties you can't switch back and forth between something 
being a property function and a variable - which is one of the main points of 
properties in the first place. With explicit properties, it's possible.

Also, I think that there's real value from an API perspective to mark what is 
and isn't intended to be used as a property.

- Jonathan M Davis