“Account Locked”

Technically speaking, in pure functional programming there is no mutation, and by definition, no state. While you can do pure functional programming in Swift, we are promoting what we consider to be a more general and flexible cure for most of the ills addressed by pure functional programming: instead of eliminating mutation, eliminate sharing by using value types. Immutable types (including classes) are just a special case of value types, since in Swift you can only do mutation by assignment and all effects are local (and then you can use let bindings to prevent assignment). Using value types gives you scalable control over mutation without the kind of hoop-jumping and inefficiency that sometimes results from being locked into total immutability. I recommend the Building Better Value Types in Swift talk from WWDC 2015 for more on this.All that said, having some kind of pure annotation for functions, methods, and closures has some real potential benefits; I expect we'll continue to look at such featu

I noticed this happening as well. My top three folders on my machine account for 370gb, but the machine says I am using 440gb. I have been rooting around but I cannot find where this space is going.

For those interested in the StoreKit flow -The “store kit flow”, is a process taken at the time of an attempt to purchase an in app purchase item such that the store kit determines that there is a problem with the user’s storekit account - for example, when the credit card information has expired. When this issue is detected, the user is given the option to be taken to the App Store app to update their account information.It used to be that the StoreKit would alert the user and ask them to fix the issue in the App Store app, when the issue was detected. Beginning with iOS 7, this check won’t bother the user until an actual charge is attempted - either when an app is requested for download or when a user attempts an in app purchase.When such a purchase is attempted (application makes the addPayment call and the user credentials are checked), and the store detects the account problem the StoreKit flow process occurs. The process begins with an initial purchase transaction result as a

The first beta release of El Capitan has so far been the most unstable version of OS X I've ever seen. Far worse on my system (2009 MacBook Pro) than Yosemite. It locks up hard just about once a day, and I have no idea what is locking it up. Graphics corruption in various places, mostly seen in Safari, embedded videos and such. I really wouldn't recommend any early beta versions of OS X to anyone that only has one machine available or anyone that doesn't have multiple full backups to restore from. That's my 2 cents so far. Hopefully all my crashing is helping Apple find some of the bugs.

Pretty sure the new watch config profile is pointing to the old one still:https://developer.apple.com/services-account/download?path=/WWDC_2015/watchOS_2_beta/watchOS_2_beta.mobileconfigDate modified is June 7th still. I'm in the same boat as I can't get the update to show up yet...

Doesn't look like it, no. TaiG just released a jailbreak though, so it's possible that, if Apple haven't already patched it, that they will hold off until they do.Against that speculation is that 8.4 is already patched (which would account for why JB was released today)