I can't reproduce this in simple tests—not quite the situation you're setting up, but just xcrun -sdk iphonesimulator /path/to/built/swiftc -parse with a very recent built-by-hand Swift. Is there anything else in your project?

@belkadan I can reproduce reliably in an actual iOS project. I've uploaded one. It's basically a one-liner:

import UIKit

class ViewController: UIViewController {

    override func viewDidLoad() {
        super.viewDidLoad()
        _ = UIColor(red:0.5, green:0.6, blue:0.7, alpha:1.0) // error
    }

}

This is Xcode in El Capitan with the 05-03 toolchain, so if you don't see the same thing, maybe it's been fixed in the daily build?

I'm still not seeing this. Xcode 7.3.1 (7D1014), with iOS SDK 13E238 (xcodebuild -version -sdk iphoneos), and the 2016-05-03 toolchain from swift.org.

…aha, wait, it compiles cleanly, but Live Issues is showing an error. And now I see we have an overload that takes Float parameters, which comes from the implementation of ColorLiteralConvertible, which no longer has argument labels that distinguish it from a non-literal initializer. @tkremenek, what do you want to do about this?

The "compiles cleanly" part is a bit strange too. Might be compiler non-determinism.

Interestingly, I can work around this by casting just the first argument, i.e. UIColor(red: 0.5 as CGFloat, green: 0.6, blue: 0.7, alpha: 1.0)

I believe that this is a known bug (that we really need to fix) where the initializer for the playground literal for colors is ambiguous with the normal init. We should rename the init method in the playground literal protocol.

@rjmccall did you just fix this?

Yes, this is fixed now.

Thanks, now that the May 31 toolchain is out I can confirm this is fixed.