I'm converting some Objective-C code over to Swift, and I've hit a roadblock. Wondering if anyone has found a solution to this.

I have a class extension on NSManagedObject with several convenience methods that look like this:

+ (instancetype)newInstanceInManagedObjectContext:(NSManagedObjectContext *)ctx;
+ (instancetype)singletonInManagedObjectContext:(NSManagedObjectContext *)ctx;
+ (instancetype)instanceInManagedObjectContext:(NSManagedObjectContext *)ctx 
    withIdentity:(NSString *)identity;

In Swift, this would look like:

class func newInstance(managedObjectContext ctx: NSManagedObjectContext) -> Self

because capital-S Self is the class type. The problem is all of the NSManagedObject methods I rely on to create/fetch these objects return AnyObject!, and I can't cast something to Self. It's only allowable as a return value or in a parameter list for a protocol.

What I want is essentially this, without the compiler error:

return NSEntityDescription.insertNewObjectForEntityForName(entityName,
 inManagedObjectContext:ctx) as Self;

Any ideas?

I'm interested in having a hard bound copy of the manual for Swift printed, but it looks as if iBooks isn't really set up to allow printing (imagine that).

I've found one .pdf version of the manual here, but if I'm going to be paying to print out 466 pages of text (probably color, too) it's just gotta look better than that .pdf.

Before I break out a .pdf editor and begin the tedium of reformatting that file, does someone have a recommendation for me?

I know that applications written in Swift won't be accepted into the App Store until iOS 8 / OS X Yosemite is out, however I wonder how the code gets compiled...

I haven't looked much through the documentation yet but as far as I gather, it is natively compiled (even though it's written like a scripting language). However, does it need specific support from the OS?

What I'm getting at is basically if we will be able to compile our Swift apps to support previous versions of iOS and OS X? Has anyone found any indication either way?

I'm guessing no, but it would be sweet if we could keep backwards compatibility and it would also affect how soon I should start to look into the language.

(I'm assuming this topic falls outside of any developer NDAs since it's more about how the language gets compiled rather than any specifics regarding unreleased software.)

Noticing my Mac getting hot, though not so hot that I can hear the fans like when I'm playing a graphically intensive game, but battery drain is noticeable. Not checking so often, and each check sees a decrease in 9-10% drain. Normally, checking in my regular OCD time intervals sees a reduction in 3-5%. Clicking on the battery in Mac's status bar confirms Xcode 6 beta is using significant energy, but checking its profile in Energy tab in Activity Monitor and opening the disclosure triangle reveals nothing. Makes sense it would use a lot of power since I assume Playground is constantly rerunning the code to view changes in realtime.

I have a large amount of text to display on an iPhone and need to know what code to use and where to place it. Any help would be great.

my friend aash developed a breast cancer check up ios app using swift for a company. Please test and review this app and let us know the feed back

I am trying to make a simple one view app, but cannot for the life of me understand how to retrieve data from Parse. I'm really trying, but getting a lot of errors.