Home/ Questions/Q 7433513
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-29T09:41:01+00:00

On some intuitive (perhaps wrong) idea of performance, I always get a copy of

  • 0

On some intuitive (perhaps wrong) idea of performance, I always get a copy of a mutable instance before I store it. So if a property expects an NSArray I take the mutable array I’m working with and store it as self.array = mutableArray.copy (though the property is specified as strong or retain).

This seems silly to me, suddenly, but is it? Do mutable instances — doing the exact same task — perform the same?

Note: The mutable instance falls out of scope and (thanks to ARC) gets released right after this, so there’s no worry that it’ll be mutated once it’s assigned to the property.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    NSArray and NSMutableArray are both (as far as I’m aware) implemented on top of CFArray, which simply has a flag specifying whether it’s mutable. CFArray functions which require a mutable array have an assertion right at the beginning, checking that flag:

    void CFArraySetValueAtIndex(CFMutableArrayRef array, CFIndex idx, const void *value) {
    // snip...
    CFAssert1(__CFArrayGetType(array) != __kCFArrayImmutable, __kCFLogAssertion, "%s(): array is immutable", __PRETTY_FUNCTION__);

    Mutable and immutable CFArrays are identical other than passing or failing this assertion, and so should NSArrays and NSMutableArrays be, performance- or other-wise.

    • 0