Bad Practice to use Nullable<T> with Value Types?
<p>Does maintenance become a nightmare on code that allows a nullable type of a value type?  I realize that <code>int?</code> is the equivalent of <code>Nullable&lt;int&gt;</code>, but my question is more geared towards the usability of it.  We see value types and naturally overlook them as not allowing <code>null</code>.  But bringing in the <code>Nullable&lt;T&gt;</code> with a shorthand of the question mark, it's obvious what it does but not always noticeable.</p>

<p>Is this one of those features that just because you <em>can</em> do it, doesn't mean you <em>should</em>?</p>

<p>What should be the preference?  A default value of a value type (i.e. <code>int SomeConfigOption = -1;</code>) or utilizing <code>Nullable&lt;T&gt;</code> (i.e. <code>int? SomeConfigOption;</code>)?</p>
