missing package product

The API isn't quite as native as a lot of us were hoping, but there are ways around some of the limitations. For example custom drawing is possible by drawing an image and loading it into an image control, which is sufficient for a lot of situations. Arbitrary positioning of views is another matter with the flow approach to layout, but you might be able to do something with a bit of creativity. For games I'd imagine it's more a case of what can I do with these limitations rather than how do I do what I would like to do. The video on layout and animations would probably be a good start to see what is possible:https://developer.apple.com/videos/wwdc/2015/?id=216As someone who spent months on a version 1 watch app I was actually quite happy to see how version 2 apps work. I was worried that I would have to rewrite a lot of code if the layout scheme was changed, but the way Apple have designed it means that this is hopefully not the case. I'd imagine that a future version of watchOS will allow arbitrary positioni

I have a iPhone 5s and mine seems to be missing too. I have restarted mine a few times, but it hasn't re appeared. I can still install apps from spotlight, I just can't find or access the App Store.

Multiple inheritance isn't supported in ObjC or Swift, but that doesn't mean it's impossible in OOP; C++ has supported multiple inheritance for a LONG time.Anyhow, you missed my point.Generics allow you to constrain to specific, homogeneous types.func foo<T>(items: [T]) { ... }Items must be an array made up of items of T.func foo(items: [T]) { ... }If T is a protocol, then items can be an array made up of anything that conforms to T. This was talked about in the talk when walking through the historical issues with OOP.Another example where the combination of protocol extensions and a generic type system really compliment one another:extension Equatable where Self : Drawable { func isEqualTo(other: Drawable) -> Bool { guard let o = other as? Self else { return false } return self == o } }That protocol extension is not possible to write without generics.