Currently it only calls setValue for single-value options and for array options.
For Collections and Maps, the interpreter only calls the getter and then adds values to the returned mutable data structure.

To provide a consistent protocol for custom bindings, it is better to always call the setter when the value of an option or positional parameter is modified.