title: When is using the C# ref keyword ever a good idea?
body: <p>The more I see ref used in production code, the more misuse I encounter and the more pain it causes me. I have come to hate this keyword, because from a framework-building standpoint, it seems silly. When would it be a good idea to communicate to users of your code the notion of <i>maybe</i> changing an object reference/value out from beneath them? </p>
  
  <p>By contrast, I love out keywords and I love even more when no keywords are used at all, in both cases because of the guarantees you're given when using them. Ref on the other hand makes no guarantees, except that you'll be forced to initialize the parameter before you pass it in, even though nothing may be changed about it.</p>
  
  <p>I'm no sage developer though; I'm sure it's got practically applicable uses. I'd just like to know what they are.</p>