NULL Spreads cause an exception on loops

Not sure if this should be considered a bug.

I wouldn’t classify this as a bug.

NULL typically means either:

  • there IS a problem, which stems from some other part of your patch, and we only see the consequences. Silently dealing with NULL just postpones the problem and makes it even harder to understand the original issue.

  • there is NO problem. The application designer decided to use NULL to encode that there is a special situation that should be addressed explicitly by the consumers of the object, which can be done by checking for IsAssigned.

1 Like

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.