Should an NSString property under ARC be strong or copy?
Objective CCocoa TouchAutomatic Ref-CountingDeclared PropertyObjective C Problem Overview
When not compiling with ARC, it is recommended to use copy properties for data types such as NSString. I could not find proper documentation on the use of copy in ARC mode. Can someone tell me what's applicable for ARC?
Objective C Solutions
Solution 1 - Objective C
It is still recommended to copy because you want to avoid something passing a mutable string and then changing it without you knowing. A copy guarantees that the string you have will not change.
Solution 2 - Objective C
Copying and ARC are orthogonal: you make copies of mutable objects to "freeze" their state; ARC keeps track of object's reference count.
NSString objects may or may not be mutable. When you receive an NSString* as a parameter, you cannot be certain that it is immutable unless you check its type (and even then you may get false positives). If your algorithm relies on the string not changing after being set, making a copy is the right thing to do. ARC, on the other hand, will ensure that the object is not released while you are holding a strong reference to it.
Solution 3 - Objective C
It doesn't matter if you're using ARC or non-ARC.
The reasoning behind the copy is so that you can guarantee that your class' internal state can't be modified from outside the implementation.
This could happen if someone passes you an NSMutableString, and then modifies it later. That consideration is independent of the memory management environment.
Solution 4 - Objective C
copy counts as strong. Use:
> @property(nonatomic,copy) NSString *name;
https://devforums.apple.com/message/654033#654033
or even:
> @property NSString *firstName;