This isn’t a problem: public interface IReadOnly { Data Value { get; } } internal interface IWritable : IReadOnly { new Data Value { get; set; } } internal class Impl : IWritable { public Data Value { get; set; } } The Impl.Value property implementation takes care of both IReadOnly.Value and IWritable.Value, as demonstrated … Read more
I looked deeper into this and played with typescript Playground. I declared two classes one with getter and the second with get method as described in your questions. Lets see how it looks like: In the first example we declared a method for getting the property value in the following way: class Greeter { greeting: … Read more
I think you’re looking for getOwnPropertyDescriptor?
There is a “standard” pattern for getters and setters in Java, called Bean properties. Basically any method starting with get, taking no arguments and returning a value, is a property getter for a property named as the rest of the method name (with a lowercased start letter). Likewise set creates a setter of a void … Read more
self.myString = @”test”; is exactly equivalent to writing [self setMyString:@”test”];. Both of these are calling a method. You could have written that method yourself. It might look something like this: – (void)setMyString:(NSString*)newString { _myString = newString; } Because you used @synthesize, you don’t have to actually bother writing that method, you can just allow the … Read more
There are two distinct forms of “properties” that turn up in the standard library, which I will categorise as “Identity oriented” and “Value oriented”. Which you choose depends on how the system should interact with Foo. Neither is “more correct”. Identity oriented class Foo { X x_; public: X & x() { return x_; } … Read more
I’m not sure if you’d consider it ‘standard’, but Project Lombok addresses this problem. They use annotations to replace much of the verbosity of Java. Some people are looking at alternative Java sibling languages, such as Groovy or Scala. I’m afraid it will take some years -if at all- before the JSR figures out a … Read more
Here is the justification from the JAXB specification – page 60. Design Note – There is no setter method for a List property. The getter returns the List by reference. An item can be added to the List returned by the getter method using an appropriate method defined on java.util.List. Rationale for this design in … Read more
As others have mentioned, if you annotate a property getter method, then Hibernate uses the setter when reading values from the database. Basically, Hibernate assumes that anything that it is writing to the database will eventually need to be read from the database. This implies that if you annotate a getter, then it needs to … Read more
I think a bit of code will help illustrate what setters and getters are: public class Foo { private string bar; public string GetBar() { return bar; } public void SetBar(string value) { bar = value; } } In this example we have a private member of the class that is called bar. The GetBar() … Read more