Re: [swift-users] Improving compilation times?

> On Mar 23, 2017, at 10:02 AM, piotr gorzelany > wrote: > > I tried using it with the latest Xcode release (version 8.2). That was released prior to the addition of the new option. Recent snapshot builds from https://swift.org/download/#snapshots

Re: [swift-users] Improving compilation times?

I tried using it with the latest Xcode release (version 8.2). W dniu czw., 23.03.2017 o 17:57 Mark Lacey napisał(a): > On Mar 23, 2017, at 1:58 AM, piotr gorzelany > wrote: > > Hi Mark, > > Thanks for the answer, its great to know that somebody

Re: [swift-users] Improving compilation times?

> On Mar 23, 2017, at 1:58 AM, piotr gorzelany > wrote: > > Hi Mark, > > Thanks for the answer, its great to know that somebody is working on it! > > I tried to add the -Xfrontend -debug-time-expression-type-checking in Xcode > in the Other Swift Flags section but

Re: [swift-users] Generic and Nested Types

On 23 Mar 2017, at 08:55, Седых Александр via swift-users wrote: > Please explain me, why we can't make Nested Types in Generic Types? I believe you can in the latest Xcode 8.3 beta. This is courtesy of SR-1446. Share and

Re: [swift-users] Improving compilation times?

Rien, You can also add the flag -Xfrontend -warn-long-function-bodies=100 directly to Other Swift Flags in Xcode. Xcode will then generate warnings for each function that compiles more than the specified amount of time (milliseconds) you supplied in the parameter (100 in this case). Regards,

Re: [swift-users] Asynchronous error recovering with RecoverableError

I'd like to bump this issue, since it has been some time and it hasn't been addressed. Thanks, Elia Cereda > Il giorno 03 mar 2017, alle ore 21:33, Elia Cereda ha > scritto: > > I’m wondering why the resultHandler block on >

Re: [swift-users] Generic and Nested Types

Which you? Zhaoxin On Thu, Mar 23, 2017 at 4:55 PM, Седых Александр via swift-users < swift-users@swift.org> wrote: > Hello. Please explain me, why we can't make Nested Types in Generic Types? > > > > -- > Седых Александр > > ___ > swift-users mailing

Re: [swift-users] Improving compilation times?

Hi Mark, Thanks for the answer, its great to know that somebody is working on it! I tried to add the -Xfrontend -debug-time-expression-type-checking in Xcode in the Other Swift Flags section but that gives me an error when compiling :0: error: unknown argument:

[swift-users] Generic and Nested Types

Hello. Please explain me, why we can't make Nested Types in Generic Types? -- Седых Александр___ swift-users mailing list swift-users@swift.org https://lists.swift.org/mailman/listinfo/swift-users

Re: [swift-users] Improving compilation times?

> On Mar 23, 2017, at 12:32 AM, Rien via swift-users > wrote: > > >> On 23 Mar 2017, at 08:27, David Hart wrote: >> >> Yes, it's best to avoid concatenating strings with +. Not only for >> performance reasons, but it's also less readable than

Re: [swift-users] Improving compilation times?

> On 23 Mar 2017, at 08:27, David Hart wrote: > > Yes, it's best to avoid concatenating strings with +. Not only for > performance reasons, but it's also less readable than string interpolation: > > str += "No: \(count), HostIp: \(clientIp ?? "?") at port: \(service ??

Re: [swift-users] Improving compilation times?

Yes, it's best to avoid concatenating strings with +. Not only for performance reasons, but it's also less readable than string interpolation: str += "No: \(count), HostIp: \(clientIp ?? "?") at port: \(service ?? "?")\n" > On 23 Mar 2017, at 08:11, Rien via swift-users

Re: [swift-users] Improving compilation times?

Thanks for that link, used it to track down the worst compile time offender: This piece of code: public func logAddrInfoIPAddresses(_ infoPtr: UnsafeMutablePointer) -> String { let addrInfoNil: UnsafeMutablePointer? = nil var count: Int = 0 var info: UnsafeMutablePointer =