[swift-users] Getting ambiguous error only when override Int decoder

I'm trying to override some decode parsers from KeyedDecodingContainer, but I getting a stranger ambiguous error. Is stranger for me, because I'm getting this message error only on *Int* and *Double* override parse. I appreciate any help because I don't know why the Float parse works and Int got

[swift-users] Was the String contains(_:) method changed in Swift 4?

I am looking at the latest version of the “App Development with Swift” iBook on page 122. There’s a code example I’ll paste below. “Maybe you want to check if one string is somewhere within another string. You can use the contains(_:) method to return a Boolean value that indicates whether or

Re: [swift-users] Cancelling an SPM build cleanly

> On Nov 7, 2017, at 10:25 AM, Geordie J wrote: > > I was just reminded of this issue by another thread (thanks Daniel Dunbar for > https://github.com/apple/swift-llbuild/pull/196 > !) > > Is it possible to cancel an SPM

Re: [swift-users] xcode 9 new build system too aggressive?

> On Nov 7, 2017, at 10:18 AM, David Baraff wrote: > > Ah. i hadn’t thought about the fact that often-time my first attempt to > build fails. that might well be the deciding thing. > any idea how long before this will show up in a release xcode? weeks? > months? a

[swift-users] Cancelling an SPM build cleanly

I was just reminded of this issue by another thread (thanks Daniel Dunbar for https://github.com/apple/swift-llbuild/pull/196 !) Is it possible to cancel an SPM build cleanly? If I run swift build and then press Ctrl-C halfway through I end up

Re: [swift-users] بخصوص: About Swift Package Manager and LLDB

Hey Fadi, do you think you can thread this email thread a little better? Right now (for whatever reason) a bunch of your emails are getting new threads in mail. It would be a lot easier to track/respond to the email if you always responded in the same mail thread. [Just friendly advice = )]

Re: [swift-users] xcode 9 new build system too aggressive?

Ah. i hadn’t thought about the fact that often-time my first attempt to build fails. that might well be the deciding thing. any idea how long before this will show up in a release xcode? weeks? months? a year? Begin forwarded message: > From: Daniel Dunbar >

Re: [swift-users] xcode 9 new build system too aggressive?

This does sound like a serious bug (and may be one I just fixed https://github.com/apple/swift-llbuild/pull/196), but if its specific to an Apple product please report bugs in Xcode on http://bugreporter.apple.com - Daniel > On Nov 6, 2017, at 10:11 PM, David Baraff via swift-users >

Re: [swift-users] بخصوص: About Swift Package Manager and LLDB

Interesting... You might want to add these discoveries to the SR that I mentioned, or file a new one with these comments. At this point you're trying to help out the folks working on SPM and a bug report is a more direct way to do that than the swift-users list. Jim > On Nov 7, 2017, at

[swift-users] بخصوص: About Swift Package Manager and LLDB

Some information may be leading to resolve of this problem I think "ld" tool does a lot of the trick Notice the difference between the results of the two compilations (Xcode and SPM): Kitura example via Xcode, when invoked "target modules list" on lldb Gets this[ 0]