c# - Is there a performance degradation when we ALWAYS use nullable value types instead of value types? -

is there performance degradation when use nullable value types instead of value types?

as mitch wheat pointed above, no, should not worry this. i'm going give short answer reason now, , later i'm going discover more you're asking:

write code correct. profile after writing find points causing grief.

when have code uses nullable , have performance reasons , profile , can't find problem yourself, then come ask how make faster. no, overhead of using nullable intents , purposes not degrading.

discover more you're asking:

• performance surprise "as" , nullable types
• why shouldn't use nullable types in c#
• c# performance gain returning nullable type sqldatareader
• alternatives nullable types in c#
• casting (int?)null vs. new int?() - better?
• boxing / unboxing nullable types - why implementation?

now, having read pages, hope feel more enlightened.