• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Swift and Threads
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Swift and Threads


  • Subject: Re: Swift and Threads
  • From: Jens Alfke <email@hidden>
  • Date: Mon, 12 Sep 2016 12:08:41 -0700

> On Sep 12, 2016, at 11:11 AM, Quincey Morris <email@hidden> wrote:
>
> My understanding is that pure Swift arrays (that is, *not* bridged NSArrays) are stored as efficiently as C arrays.

It’s not the efficiency of storage I was concerned about; in this case it’s the COW semantics, which can involve the data backing store being moved at the whim of an opaque internal implementation.

If you want just a plain raw array without that sort of behavior, I’m not sure how you would do it in Swift without resorting to UnsafePointer shenanigans.

—Jens
_______________________________________________

Cocoa-dev mailing list (email@hidden)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden


References: 
 >Swift and Threads (From: "Gerriet M. Denkmann" <email@hidden>)
 >Re: Swift and Threads (From: Jens Alfke <email@hidden>)
 >Re: Swift and Threads (From: Jens Alfke <email@hidden>)
 >Re: Swift and Threads (From: Quincey Morris <email@hidden>)

  • Prev by Date: Re: Swift and Threads
  • Next by Date: Re: Linking against AVKit breaks app on 10.6
  • Previous by thread: Re: Swift and Threads
  • Next by thread: Re: Swift and Threads
  • Index(es):
    • Date
    • Thread