{"push_id":1445065414,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"364fe874cd63f8f071b2f08206c19cf9acebebec","before":"2f8136a3d49d44a9b7d3d936ebc1a6612ac803c2","commits":[{"sha":"364fe874cd63f8f071b2f08206c19cf9acebebec","author":{"name":"Chris Hamons","email":"40a2251c604dbcb62f6bc7e7ada57eef631106fa@xamarin.com"},"message":"[XM] Fix Argument Semantics on NSTextContainer.TextView (#1309)\n\n- https://bugzilla.xamarin.com/show_bug.cgi?id=43236\r\n- In Xcode 8b3, Apple changed this property to depend on the deployment target\r\n  for weak/strong'ness\r\n\r\n  +#if MAC_OS_X_VERSION_MIN_REQUIRED < MAC_OS_X_VERSION_10_12\r\n   @property (nullable, strong) NSTextView *textView;\r\n   +#else\r\n   +@property (nullable, weak) NSTextView *textView;\r\n   +#endif\r\n    @end\r\n- We could parse the MacO headers to get this and change\r\n strong/weak'ness but:\r\n- It is easier to default to weak, the \"safe\" option. It introduces a possible\r\n leak but you can null it out in that rare case.\r\n- If Apple does this more regularly, we may have to readdress","distinct":true,"url":"https://api.github.com/repos/xamarin/xamarin-macios/commits/364fe874cd63f8f071b2f08206c19cf9acebebec"}]}
{"actor":{"display_login":"rolfbjarne"}}