When you need to get external input for `set` and `init` methods defined for properties and indexers or for `remove` and `add` methods for events, you should
always get this input throught the `value` contextual keyword.
The contextual keyword `value` is similar to an input parameter of a method; it references the value that the client code is attempting to assign to the property, indexer or event.
The keyword `value` holds the value the accessor was called with. Not using it means that the accessor ignores the caller's intent which could cause unexpected results at runtime.
This rule doesn't raise an issue when the setter is empty and part of the implementation of an `interface`. The assumption is that this part of the interface is not meaningful to that particular implementation. A good example of that would be a "sink" logger that discards any logs.
\[~tamas.vajk] 10min seems like a high remediation cost. Does that mean that the Compliant Solution I added is off-base?
=== on 20 Jul 2015, 11:59:05 Tamas Vajk wrote:
\[~ann.campbell.2] We can reduce the required time.
=== on 20 Jul 2015, 13:53:16 Ann Campbell wrote:
I halved it to 5min, [~tamas.vajk]
=== on 27 Jul 2015, 15:39:03 Ann Campbell wrote:
\[~dinesh.bolkensteyn] note that I've edited the first line. Your version, "a property and indexer ``++set++`` method" speaks of one, collective method for both a property and an indexer at one time.
=== on 27 Jul 2015, 15:44:58 Dinesh Bolkensteyn wrote: