title: C#: interface inheritance getters/setters
body: <p>I have a set of interfaces which are used in close conjunction with particular mutable object.</p>
  
  <p>Many users of the object only need the ability to read values from the object, and then only a few properties.  To avoid namespace pollution (easier intellisense) and to get across the usage intent, I'd like to have a small base interface which only exposes a few "key" properties in a read-only fashion.</p>
  
  <p>However, almost all implementations will support the full interface, which includes modifiability.</p>
  
  <p>Unfortunately, I ran into a roadblock expressing that concept in C#:</p>
  
  <pre><code>interface IBasicProps {
     public int Priority { get; }
     public string Name {get;}
     //... whatever
  }
  
  interface IBasicPropsWriteable:IBasicProps  {
     public int Priority { set; } //warning CS0108: [...] hides inherited member [...]
     public string Name { set; }
     //... whatever
  }
  </code></pre>
  
  <p>I certainly wasn't intending to hide any members, so that aint good!</p>
  
  <p>Of course, I can solve this using methods just fine, but what's the <em>right</em> choice?  I'd like to keep the "core" interface as small as possible even if splitting the interfaces serves no purpose other than communicating intent.  With split interfaces, it's just really obvious which methods aren't going to do any updating, and it makes writing code a bit clearer (not to mention also allows nice-n-simple static singleton stubs that suffice for quite a few simple cases).</p>
  
  <p>I'd like to avoid any abstract classes and the like; they make reimplementation or quick single-purpose shims all that more complex and hard-to-grok.</p>
  
  <p>So, ideas?</p>