• 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: Quincey Morris <email@hidden>
  • Date: Tue, 13 Sep 2016 00:43:22 -0700
  • Feedback-id: 167118m:167118agrif8a:167118sE7JjjSVJy:SMTPCORP

On Sep 12, 2016, at 23:52 , Gerriet M. Denkmann <email@hidden> wrote:
>
> I tried a variation of my function. This does not crash (not even in Debug builds), but takes twice the memory and is about four times slower:

I no longer understand what we’re doing here. Based on the code you’ve posted, it looks like you’re approaching a multithreaded optimization problem by microbenchmarking fake code, using implementation-dependent data structures whose characteristics are not governed by an API contract, and ignoring thread safety. How can that possibly lead to a design for your real code? What kind of advice (if any) are you seeking?

_______________________________________________

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: "Gerriet M. Denkmann" <email@hidden>)

  • Prev by Date: Re: Swift and Threads
  • Next by Date: Re: Swift and Threads
  • Previous by thread: Re: Swift and Threads
  • Next by thread: Re: Swift and Threads
  • Index(es):
    • Date
    • Thread