Re: [swift-users] Initializing a UIColor

> On May 11, 2016, at 7:37 AM, Erica Sadun via swift-users > wrote: > >> >>> On May 11, 2016, at 9:57 AM, Dennis Weissmann >> > wrote: >>> >>> Huh! There’s a new overload for that initializer: >>> >>> >>>

Re: [swift-users] swift redistributable without Xcode

Or better yet. What is the command that is used to build the downloadable swift packages for OSX? I can go from there probably. -tim On 5/11/16, Tim Prepscius wrote: > Also, > > So I build the thing, and I move over the swift directory to a > computer without Xcode. > >

Re: [swift-users] swift redistributable without Xcode

Also, So I build the thing, and I move over the swift directory to a computer without Xcode. I run bin/swift and get: swift-macosx-x86_64 tim$ bin/swift *** You are running Swift's integrated REPL, *** *** intended for testing purposes only. *** *** The full REPL is built as part of

Re: [swift-users] SubSequence Index bug in generic functions?

Filed as: SR-1487 > On May 11, 2016, at 1:51 PM, Dmitri Gribenko wrote: > > On Wed, May 11, 2016 at 1:48 PM, Hooman Mehr via swift-users > wrote: >> The reason this is appearing here before filing a radar is

Re: [swift-users] SubSequence Index bug in generic functions?

On Wed, May 11, 2016 at 1:48 PM, Hooman Mehr via swift-users wrote: > The reason this is appearing here before filing a radar is getting a quick > feedback as I have been assuming this is the expected behavior but Nate Cook > told me otherwise. See this thread for the

[swift-users] SubSequence Index bug in generic functions?

The reason this is appearing here before filing a radar is getting a quick feedback as I have been assuming this is the expected behavior but Nate Cook told me otherwise. See this thread for the initial

Re: [swift-users] swift redistributable without Xcode

Ok, so when I build finally it: du -h -d 1 3.7M./cmark-macosx-x86_64 81M./llbuild-macosx-x86_64 5.6G./lldb-macosx-x86_64 7.9G./llvm-macosx-x86_64 18M./ninja-build 8.4G./swift-macosx-x86_64 47M./swiftpm-macosx-x86_64 22G. 22 gigs is a bit much? Even the

[swift-users] Cross-Compiling For ARM Linux

Hi all, Perhaps this has been discussed a lot already, but I'm a bit lost as to the current state of cross-compiling Swift source code from x86_64 Linux to ARM Linux.Given the documentation for cross-compiling for Android, it seems that there is some cross-compiling support, but I'm

Re: [swift-users] swiftc and CocoaPods modules

I just realized the text formatting is wrong, sorry for that. 2016-05-09 11:17 GMT-03:00 Marcel Rebouças : > Hello all, > > I'm trying to run the swiftc (a modified one) command in a project folder > in order to compile all .swift files. It is currently working as follows:

Re: [swift-users] Initializing a UIColor

I agree, however, I like your workaround better than all the extra parentheses and CGFloats! > On May 11, 2016, at 10:37 AM, Erica Sadun wrote: > >> >>> On May 11, 2016, at 9:57 AM, Dennis Weissmann >> >

Re: [swift-users] Initializing a UIColor

> >> On May 11, 2016, at 9:57 AM, Dennis Weissmann > > wrote: >> >> Huh! There’s a new overload for that initializer: >> >> >> >> The one that takes CGFloats is the one that was there before, but the one >> taking Floats is new!

Re: [swift-users] Initializing a UIColor

Huh! There’s a new overload for that initializer: The one that takes CGFloats is the one that was there before, but the one taking Floats is new! You can work around like this: let color = UIColor(red: CGFloat(0.892), green: CGFloat(0.609), blue: CGFloat(0.048), alpha: CGFloat(1.000)) or

[swift-users] Initializing a UIColor

The following code worked fine in previous development snapshots but fails in the May 9, 2016 snapshot: let color = UIColor(red: 0.892, green: 0.609, blue: 0.048, alpha: 1.000) Does anyone know whether this is a bug or if the syntax changed? (Yes, I imported UIKit). Xcode gives an