Swift 6

Reposting this with more info:When the beta came out yesterday, I did an upgrade and not a restore. Today I litterally watched the battery percentage drop 1 percent every two minutes while I only had the home screen active (background apps disabled, location services disabled, etc). I kept checking the Settings -> Battery page and it show Home Screen at 15% of the usage, which was completely wrong.Today I did a complete restore and now things are better. The Settings -> Battery screen not only showed Photo App as the top user (I have over 8 gigs of phots and videos), but it also showed it as Background Activity. I didn't see that before I did the complete restore. Now, Mail, Messages and Calendar also show that. I'm sure the battery will still drain faster than with a production version, but at least it seems like the reporting is working correctly and it allowed me to understand what was sucking the life out of my battery.---------------------------------------------------------As an update, I have an

Mine is stuck on a 3/4 finished ring. The second ring during the update - the first ring completed and the watch reset itself after that and started on a second ring (which is stuck). The iPhone 6 came back and said the Watch has been updated. I'm scared to touch it in case it just extremely slow - I think I'm stuck though. Thanks, Cory

> Is this possible now ? Planned for future Swift 2.x version ?I hope so - I was just trying to do exactly that, too.For the moment I worked around it by using separate getXXX and setXXX methods instead of having a computed property. But that's not ideal

bump. anyone with a solution or options, still haven't been able to download anything: xcode, ios9, swift, wOS2

Also.... I found a very informative website that has a ton of examples specifically on how to work with dates within Swift.Here's a code snippet that he uses as an example, but does not compile for me, and I have no idea why I get the error: could not find member 'CalendarUnitDay'. Was this syntax changed with Swift 2.0?Every example I could find uses this syntax, but for me... no luck.// Playground - noun: a place where people can play import UIKit let userCalendar = NSCalendar.currentCalendar() // Let's create some dates to work with // ==================================== // It's 3:45:30 a.m., New Year's Day. Time to go home. let goHomeYoureDrunkTimeComponents = NSDateComponents() goHomeYoureDrunkTimeComponents.year = 2015 goHomeYoureDrunkTimeComponents.month = 1 goHomeYoureDrunkTimeComponents.day = 1 goHomeYoureDrunkTimeComponents.hour = 3 goHomeYoureDrunkTimeComponents.minute = 45 goHomeYoureDrunkTimeComponents.second = 30 let goHomeYoureDrunkTime = userCalendar.dateFromComponents(goHomeYoureDru

They renamed some enums / options to be more consistent.In Swift, it would now be NSCalendarUnit.Year (type NSCalendarUnit, case .Year). If you double command-click on NSCalendarUnit (or NSYearCalendarUnit) in Xcode in your playground, it will pull up the Swift version of the header.And as far as the example code goes, OptionSets are handled differently now in Swift 2.0 and use set syntax instead of bitwise operators to join and test them.See the Xcode 7 beta release notes or https://forums.developer.apple.com/thread/3623 for more info on that.