title: When designing an OO language, should I avoid write-only properties?
body: <p>I am designing an object-oriented programming language for the purpose of learning. The language has properties, like this:</p>
  
  <pre><code>Class Fruit:
    Property ReadWrite Float weight
    Property WriteOnly Integer someWriteOnlyProperty # &lt;-- avoid?
  </code></pre>
  
  <p>Should I add the option for write-only properties or will this only lead to bad design decisions in programs using this language?</p>