Open Radar

 
Summary:
Parameters of Objective-C methods are converted into assumed variables, which might increase the risk of crashes significantly.
take for example the UIApplication delegate methods looks as such:
func application(application: UIApplication!, didFinishLaunchingWithOptions launchOptions: NSDictionary!) -> Bool

Now launchOptions is in many cases a nil value, which will crash when accessed incorrectly. In fact it cannot be "assumed" that the parameter is not nil!

I would expect methods from Cocoa to either use optional or unpacked parameters and converted Objective-C methods to always use optionals.

Same goes for return-types.
It is in fact a common use case in objective-c to return nil, which

Steps to Reproduce:
1. Write this method in an objecive-c protocol
- (NSArray*)parseWithText:(NSString*)text;
2. Add protocol to bridging header
3. Implement function in a class



Expected Results:
Func should ideally look like this:
func parseWithText(text: String?) -> [AnyObject]?


Actual Results:
func parseWithText(text: String!) -> [AnyObject]!