[swift-users] Latest development code fails to build

Every time I try to build any app in Xcode 7.3 with the latest development snapshot (Apr 12), the build fails with this error: `Command failed due to signal: Illegal instruction: 4` Anyone else seeing this? The default and the 2.2.1 snapshot works fine. Regards, Chuck Lane _

Re: [swift-users] Latest development code fails to build

Actually, you don’t have to write any code. Just make a new project using a single view application and try to build it. I’ve re-downloaded the developer build and even downloaded Xcode again from the App store. Here is the error that Xcode reports: CompileSwift normal x86_64 /Users/charleslan

Re: [swift-users] Latest development code fails to build

Excellent! Thanks, I thought I was going crazy since I didn’t see any other reports about this. I assume we’ll see a new snapshot posted at some point then? Regards, Chuck Lane ___ swift-users mailing list swift-users@swift.org https://lists.swift.org/

[swift-users] Trying to learn swift 3 renamification (as mattn calls it!)

While rebuilding some apps using the new development trunk build, I figured out the naming changes to just about everything but this: let string = "Here is a string" string.drawWithRect(CGRect(x: 10, y: 10, width: 200, height: 200), options: .usesLineFragmentOrigin, attributes:

Re: [swift-users] Trying to learn swift 3 renamification (as mattn calls it!)

Thanks Erica! Sadly I don’t have it working yet. Xcode wants to insert a comma between the words ‘with rect:’ for some reason. I’ll keep at it! Regards, Chuck Lane ___ swift-users mailing list swift-users@swift.org https://lists.swift.org/mailman/listi

Re: [swift-users] Trying to learn swift 3 renamification (as mattn calls it!)

OK, I got it. Instead of string.draw(with rect: CGRect(etc. etc. etc. It’s string.draw(with: CGRect( and so on and on and on… I got no help from xcode figuring this out though! Regards, Chuck Lane ___ swift-users mailing list swift-users@swift.org https

[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 err

Re: [swift-users] Initializing a UIColor

gt; 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 > let color = UIColor(red: Float(0.892), green: Float(0.609), blue: > Float(0.048), alpha: Float(1.000)) > > - Dennis >

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 >> > wrote: >>> >>> Huh! There’s a new overload for that i

[swift-users] Swift 3.0 Preview 1 Snapshots available!

I see that there is a ‘Trunk Development(master)’ and the 'Swift 3.0 Preview 1 Release Branch’ both from May 31, 2016. Is there any difference in these two releases? Thanks, Chuck Lane ___ swift-users mailing list swift-users@swift.org https://lists.sw

[swift-users] CoreData weirdness in development build

Here’s something ‘cute’. Make a simple ios project using coredata. Name an entity whatever you like, but give it any attribute that starts with ‘is’. Such as isVisited or isDone or whatever you like of type Boolean. Try setting the entity to true or false, no matter, and save the entity. The pr

[swift-users] CoreData weirdness in development build

OK, i tested it using a string attribute and it still fails. Coredata will crash if an attribute begins with ‘is’. > Here’s something ‘cute’. Make a simple ios project using coredata. Name an > entity whatever you like, but give it any attribute that starts with ‘is’. > Such as isVisited or isD

Re: [swift-users] CoreData weirdness in development build

Thanks Brent, sounds reasonable. Although I don’t think this was a problem in pre-Swift 3.0 builds. I think I’ll just avoid using attributes beginning with ‘is’ in the managed object model! ___ swift-users mailing list swift-users@swift.org https://lis

[swift-users] New Swift Snapshots Available!

I’m running macOS Sierra. When I set ios 10 as the deployment target, I get an error: Command failed due to signal: Illegal instruction: 4 It seems to build ok when using 9.3 or below as the build target. ___ swift-users mailing list swift-users@swift.o

Re: [swift-users] New Swift Snapshots Available!

I simply created a new single-view project targeting ios 10. I got the error immediately. > Can you reduce the problem to a small test case? Please file a bug report > onbugs.swift.org(http://bugs.swift.org)for this, and include information on > the last toolchain which worked. > > - Daniel >

Re: [swift-users] New Swift Snapshots Available!

This is with Xcode 8 beta and the June 20 Development snapshot of swift 3.0. It works fine with the default 3.0 toolchain. > Are you using Xcode 7.3? The new toolchains only support Xcode 8 (because of > SDK requirements and issues with Xcode 7's Clang). > > Jordan > > > > On Jun 21, 2016, a

Re: [swift-users] New Swift Snapshots Available!

This is a little snippet of the error : :0: error: invalid version number in '-miphoneos-version-min=10.0.0' Assertion failed: (Maj < 10 && Min < 100 && Rev < 100 && "Invalid version!"), function getDarwinDefines, file /Users/buildnode/jenkins/workspace/oss-swift-package-osx/llvm/tools/clang/lib

Re: [swift-users] New Swift Snapshots Available!

Thanks! I was kind of waiting to see if it was just something dumb that I was doing or didn’t do. But apparently you’ve seen it too. Makes me feel better :-) > Thanks Charles! I have created Jira issue to track this bug. > > https://bugs.swift.org/browse/SR-1853 > > Mishal Shah __

[swift-users] Toolchain 07/29

With Xcode Beta 3 and toolchain 07/29 the following line will cause a segmentation fault 11: func imagePickerController(_ picker: UIImagePickerController, didFinishPickingMediaWithInfo info: [String: Any]) { … … dismiss(animated: true) } You have to leave this: [Str

Re: [swift-users] Toolchain 07/29

Bug report SR-2234 has been filed. Thanks > On Jul 31, 2016, at 4:38 PM, Mark Lacey wrote: > > Can you please open a bug for this at bugs.swift.org? > > Mark > >> On Jul 31, 2016, at 13:07, Charles Lane via swift-users >> wrote: >> >> With Xcod

Re: [swift-users] Toolchain 07/29

nks! > > -- Erica > > >> On Jul 31, 2016, at 4:19 PM, Charles Lane via swift-users >> wrote: >> >> Bug report SR-2234 has been filed. >> >> Thanks >> >> >>> On Jul 31, 2016, at 4:38 PM, Mark Lacey wrote: >>> >&

Re: [swift-users] Toolchain 07/29

The 7/25 snapshot worked fine for me. The 7/29 snapshot only worked if you marked the func as @nonobjc. > 7/25 does not work for me. -- E > > > On Aug 1, 2016, at 10:51 AM, Charles Lanewrote: > > > > The 7/25 snapshot seems to work. That was before AnyObject was changed to > > Any. > > > > Re

[swift-users] Cannot implement NSURLSessionDownloadDelegate

I have the same problem except it’s with the UISearchResultsUpdating protocol. I read Jordan’s reply with the workaround but I’m not familiar enough with OBJC to implement it. Could you possibly show me the correct form for the following: func updateSearchResults(for searchController: UISearchCo