On 19 May 2015, at 05:16, Greg Parker <[email protected]> wrote: > It's probably feasible for the compiler to warn if you declare a (copy) > property of a type that conforms to NSMutableCopying, on the assumption that > -copy returns an incompatible immutable copy. You should file a bug about > that too.
I don’t understand how that would work … ? NSString conforms to NSMutableCopying as well, as that’s how you get from an NSString to an NSMutableString. The only way I see to make this work is to codify the class naming convention and warn about that. Cheers, -- Uli Kusterer “The Witnesses of TeachText are everywhere...” http://zathras.de _______________________________________________ Do not post admin requests to the list. They will be ignored. Objc-language mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/objc-language/archive%40mail-archive.com This email sent to [email protected]
