SwiftUI List performance

I noticed a lot of people having problems with Watch os2 beta 2, today i decided to buy a second watch so i could use my first one for development. The new one is running OS1.01 and it is so much faster and the battery is running great. I hope apple addresses this problem and they will get a fix soon. The performance and experience needs to be much better when the public release will be finished!Anyone found a solution or a cause for this problem?

I have tried this several times just to make sure I was doing it correctly, and I always come up with the same bad result. This is a 2013 Mac Book Air:Installed the El Capitan installer on my Yosemite system from the App StoreFormatted a brand new 128gb flash drive as Mac OS Extended (Journaled) with a GUID Partition TableInstalled the Installer on the flash drive: sudo /Applications/Install OS X 10.11 Developer Beta.app/Contents/Resources/createinstallmedia --volume /Volumes/ElCapInstaller --applicationpath /Applications/Install OS X 10.11 Developer Beta.app --nointeractionEjected the flash driveReinserted the flash drive and booted from it using the Option keyThe installation onto the flash drive proceeded and worked up to the very last, when it said Less that one second remaining. It stayed there and never finished, never rebooted. I waited what I thought ws a long time.I was able to **** off the installation log. I do see some errors that I don't know what to do with. They seem to be communications relate

With Swift 2, you can write permute() as a method on Dictionary (assume that all keys and values are unique):extension Dictionary where Value: Hashable { func permute() -> [Value: Key] { var permuted = [Value: Key]() for (key, value) in self { permuted[value] = key } return permuted } }By permute, I mean specifically that keys become the values and vice versa.But what if you wanted to write this more generically so that any sequence of (key, value) tuples in which the values were hashable could be converted to a permuted dictionary. Is it possible?I'm thinking something like:extension SequenceType where Generator.Element: (Any, Hashable) { func permute() -> [Generator.Element.1: Generator.Element.0] { ... } }Or perhaps:extension SequenceType<Key, Value: Hashable> where Generator.Element == (Key, Value) { func permute() -> [Value: Key] { ... } }But these are both nonstarters. In the first version, it's not clear what Generator.Element: (Any, Hashable) would mean, and the compiler doesn't accept

I have a few questions on Core Image, in relation to the new implementation in OS X 10.11.Can CIImages be considered thread-safe?In other words, can an identical or different CIContexts, on different threads, be accessing the same CIImage without running into problems?Are CIContexts themselves thread-safe? Even if they are, what would be the best strategy for higher performance: sharing a single CIContexts among threads that will concurrently use the context, or giving each thread its own CIContext to play with?

Good evening,I have been trying to implement handoff from my watchkit 1 extension to my iPhone app. The NSUserActivity creation works fine, the icon gets displayed on the iPhone's lock screen and my application delegate gets called with the proper activity/data.What I'm struggling with is to restore the required view controller hierarchy to resume the activity on the iPhone. I was expecting this to be as straightforward as UIKit state restoration, which I have recently implemented, but I keep hitting a wall.My app supports two activities for handoff right now: Activity A and Activity B.My view controller hierarchy is as follows:Root (UISplitViewController)1. primary (UINavigationController)index UITableViewController subindex UITableViewController details UITableViewController (see below)2. secondary (UINavigationController)details UITableViewController complete details UIViewControllerHere is my continueUserActivity function: func application(application: UIApplication, continueUserActivity userActivity: NSU