Nullability & New Attribute Objects for Objective-C Templates

[justin]

I'm working on getting our ObjC templates updates.

Here's what's new in this one:

1. I replaced the old struct objects we were using for relationship and attribute names with first class NSObject instances. This lets us not annoy the Apple gods by putting NS objects inside structs, which is a no-no in ARC land. (__unsafe_unretained is cheating)
2. Added nullability attributes where appropriate for attributes, relationships, and fetched properties.

I still want to add lightweight generic support, but that is going to require some internal surgery I think.

[rentzsch]

instancetype: sure, awesome

nullable: sure, awesome

I was initially cold to replace the Mike-Ash-style structs with full-blown classes. I don't consider __unsafe_unretained in this very specific circumstance (static objects really existing to provide a missing language feature) cheating. But I've come around and this is Core Data code where Yet Another Message Send isn't going to even appear on the final bill of goods.

[sixten]

Is there a specific reason why the primitive accessors don't get nullability annotations? It looks like optional properties still get primitives that don't allow nil values.

[rentzsch]

Hey @sixten I don't quite understand, does this fix what you are talking about? #343