These warnings came up with clang analayis on Xcode 7.3 (may have been present earlier). I think formalizing the expectations in our code is a good idea. In particular some cases where undefined behavior would have been met are now at least reasoned in the handling of nil values.
These warnings came up with clang analayis on Xcode 7.3 (may have been present earlier). I think formalizing the expectations in our code is a good idea. In particular some cases where undefined behavior would have been met are now at least reasoned in the handling of nil values.