What language decision in C# annoys you?
<p>I was just dealing with strings, and I find myself annoyed that strings can be nullable. So, I have to have </p>

<pre><code>if((teststring??string.Empty)==string.Empty)
</code></pre>

<p>all over the place. Would string? have been so hard for allowing nullability in the relatively few cases where it is needed (dbs, idiot user inputs, etc.). I also find myself irritated with having to export readonly interfaces in the cases where I want some form of const correctness. So, what C# language construct/decision annoys you?</p>

<p>EDIT: Thanks for the isnullorempty function, I hadn't seen that before! Still doesn't lessen my annoyance at it being nullable :D</p>
