Open Radar

 
Summary:
Programmer can still specify 'nonnull' annotation to a weak pointer. This is in conflict with the real behaviour of weak pointers being implicitly always nullable.

Steps to Reproduce:
Compile this code:

NS_ASSUME_NONNULL_BEGIN
 
@interface ViewController : UIViewController
 
// Note it's a weak property and compiler does not complain. 
// Anyway the property will be nullified by the runtime as it has always been. Annotations don't affect generated code.
@property (nonatomic, weak) id delegate;
 
@end
 
NS_ASSUME_NONNULL_END
 
 
// Using it:
id delegate = [[NSObject alloc] init];
ViewController *controller = [[ViewController alloc] initWithNibName:nil bundle:nil];
controller.delegate = delegate;
delegate = nil;  // controller.delegate is nil as expected. Generated code does not change.
controller.delegate = nil; // Generates warning at compile time

Expected Results:
It would be good if weak pointers are always implicitly anotated as nullable, or compiler generate a warning if programmer does not annotate as such in an annotated region.

Actual Results:
Compiler does not complain, but behaviour is correct at run time.

Version:
XCode 6.3 (6D570)

Notes:


Configuration:


Attachments: