property syntax strawman

[Daniel Keep]

Steven Schveighoffer wrote:
> So your answer is, there is no ambiguity because it's not possible to
> access the getter/setter directly?  That poses a problem for existing
> code which uses delegates to such functions.  I'm not sure we want to
> lose that ability.

You can't trivially disambiguate between the getter and the setter with
the current system, either.  How is this a new issue?

Besides which, why can't you just add this:

  __traits(getter, aggregate.property)

Problem solved.