@property get/set or public varaible?

[ketmar via Digitalmars-d-learn]

On Sunday, 4 December 2016 at 15:30:22 UTC, vladdeSV wrote:
> Are there any other reasons to use get/setters?

basically, no. as you can omit parentheses in D, converting to 
getter/setter later should be seamless.

the only reason to have getter/setter in your case is a situation 
where you may want to override 'em in child class. so if you are 
using class hierarchy, take some time to think if you will ever 
need such overrides.