On 1/24/13, Walter Bright <newshou...@digitalmars.com> wrote: > 2. the: > f = g > rewrite to: > f(g) > only happens if f is a function that only has overloads for () and (one > argument). No variadics.
This is going to be a problem in API refactoring. if "f" used to be a field but is now turned into a (potentially) expensive function call, the user will have no idea. Anyway we'll lose track of everything in this thread just like in all the other threads, so I suggest that we: - Create a new branch in DMD which will only be used to work on @property freely - Add all test-cases which are affected by this feature - Work on this branch for some time until we get a solid implementation - Discuss property enforcement on a casis-by-casis base in the forums, rather than discussing it wholesome. Special rules should be ok as long as we properly define them and document them. And later we'll merge this into master and add some solid bit of documentation to go with it. Whatever we decide it should be a result of focused work, and not executive decisions due to perceived maintenance costs. We haven't really had a focused effort on properly implementing @property, we've had sporadic pull requests instead.
