09/07/2017, 7:55 PM
Yes, that KEEP is somewhat controversial, because "implicitly optional" types (we tend to call them "nullability flexible" inside, because they are just a special case of "flexible" types) are known to be abused in Swift. I'm not quite sure it'll be accepted, I just had a "what if" moment. You really don't need such things in, like, 95% cases. Unfortunately, there're those pesky 5%.