I second getting rid of write-onle - the only real case I can think of, is
something like a password property on a user/account model-type, which gets
encrypted and thus can't be read, and as Amaury pointed out, that should be
a setPassword() method instead, perhaps even a separate
On 10/20/12 10:45 AM, Rasmus Schultz wrote:
Just drop the idea of read-only altogether, please - it's so marginally
useful in the first place, unconventional compared to other languages, and
Read-only is perfect for value objects, where the alternative is a bunch of protected
props and
