[swift-users] Assigning [Int] to [Any] crashes Swift 2.2

Just ran into a weird crash with Swift 2.2 in Xcode 7.3. It reproduces in a playground: import Foundation let a = [88] let b: [Any] = a // CRASH In my real program, the top of the crash backtrace is: * thread #1: tid = 0x460b62, 0x00010669988b libswiftCore.dylib`swift_unknownRetain + 27,

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

They come out roughly biweekly, although it depends on how stable the build is. If you hadn't seen already, there are older snapshots at the bottom of the page. Jordan > On Apr 13, 2016, at 16:45, Charles Lane wrote: > > Excellent! Thanks, I thou

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/

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

Drat, that's me. I was hoping to get out of the business of knowing UIApplicationMain's exact signature, but I guess that doesn't always work? I'll ask around for a better solution. My apologies, Jordan > On Apr 13, 2016, at 16:15, Charles Lane via swift-users > wrote: > > Actually, you don’

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

> On Apr 13, 2016, at 10:27 AM, Charles Lane via swift-users > wrote: > > 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 d

[swift-users] IBM and Swift on the Server

At QCon London earlier this year, IBM came to speak about their work with Swift on the server and their use on Linux. I interviewed them afterwards about it, and now both the presentation and interview write-up are available on InfoQ, in case you’re interested: http://www.infoq.com/presentation

[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] [swift-evolution] What about a VBA style with Statement?

> On Apr 13, 2016, at 10:08 AM, Erica Sadun wrote: > > >> On Apr 13, 2016, at 8:25 AM, Sean Heber via swift-evolution >> wrote: >> >> This pair works pretty well, too, if you don’t mind free functions: >> >> func with(inout this: T, @noescape using: inout T->Void) { using(&this) } >> func wi

Re: [swift-users] [swift-evolution] What about a VBA style with Statement?

> On Apr 13, 2016, at 9:26 AM, Sean Heber wrote: > >> On Apr 13, 2016, at 10:08 AM, Erica Sadun wrote: >> >> >>> On Apr 13, 2016, at 8:25 AM, Sean Heber via swift-evolution >>> wrote: >>> >>> This pair works pretty well, too, if you don’t mind free functions: >>> >>> func with(inout this:

Re: [swift-users] [swift-evolution] What about a VBA style with Statement?

> On Apr 13, 2016, at 8:25 AM, Sean Heber via swift-evolution > wrote: > > This pair works pretty well, too, if you don’t mind free functions: > > func with(inout this: T, @noescape using: inout T->Void) { using(&this) } > func with(this: T, @noescape using: T->Void) { using(this) } > > It wo