A difference between using a getter or setter and using a standard function is that getters/setters are automatically invoked on assignment. So it looks just like a normal property but behind the scenes you can have extra logic (or checks) to be run just before or after the assignment. So if you decide to add … Read more
Using a getter method is a better design choice for a long-lived class as it allows you to replace the getter method with something more complicated in the future. Although this seems less likely to be needed for a const value, the cost is low and the possible benefits are large. As an aside, in … Read more
I think it is actually quite a bad practice if your getter methods change the internal state of the object. To achieve the same I would suggest just returning the “N/A”. Generally speaking this internal field might be used in other places (internally) for which you don’t need to use the getter method. So in … Read more
Position the cursor inside the class, then press ALT + Ins and select Getters and Setters from the contextual menu.
“A var in a protocol with only get isn’t just a let?” No. A let indicates a constant. But that is not the case here. Consider the following: protocol SomeProtocol { var someProperty: String { get } } class SomeClass : SomeProtocol { var someProperty: String = “” func cla () { someProperty = “asd” … Read more
I don’t inline anything until a profiler has specifically told me that not inlining is resulting in a performance problem. The C++ compiler is very smart and will almost certainly automatically inline such simple function like this for you. And typically it’s smarter than you are and will do a much better job at determining … Read more
In python, you can just access the attribute directly because it is public: class MyClass: def __init__(self): self.my_attribute = 0 my_object = MyClass() my_object.my_attribute = 1 # etc. If you want to do something on access or mutation of the attribute, you can use properties: class MyClass: def __init__(self): self._my_attribute = 0 @property def my_attribute(self): … Read more
The TypeScript specification (8.4.3) says… Accessors for the same member name must specify the same accessibility So you have to choose a suitable alternative. Here are two options for you: You can just not have a setter, which means only the Test class is able to set the property. You can place a breakpoint on … Read more
Pre-C# 6 I’d use the last of these, for a trivial property. Note that I’d call this a public property as both the getters and setters are public. Immutability is a bit of a pain with automatically implemented properties – you can’t write an auto-property which only has a getter; the closest you can come … Read more
The Rails Style Guide recommends using self[:attr] over read_attribute(:attr). You can use it like this: def name name_trans || self[:name] end