Why is CoreCLR Int32.TryParse not done in the most optimal way?

[iamkisly]

Hi all. I would like to know why Int32.TryParse is designed this way.
Why is validation carried out in this place before checking the value for null? It is logical to assume that if an null object is passed, then style validation is not needed.
Maybe this reserves the possibility of expansion, but it looks very strange. Or, more likely, I don't understand what's going on here correctly :)

[stephentoub]

Because by spec an erroneous number style needs to result in an exception regardless of the string to be parsed. Otherwise, you only know that you're holding it wrong for some input strings.

[iamkisly]

OK. The answer suits me, although I think this behavior is strange :)