Re: [swift-users] Type inference issue with map and filter chained

2017-10-04 Thread Mark Lacey via swift-users
> On Sep 24, 2017, at 1:52 AM, Trevör ANNE DENISE via swift-users > wrote: > > Hello everyone, I found this on StackOverflow : > https://stackoverflow.com/questions/46381752/swift-4-methods-chaining/ >

Re: [swift-users] Type inference of array element type

2017-03-24 Thread Mark Lacey via swift-users
> On Mar 24, 2017, at 3:08 AM, Toni Suter via swift-users > wrote: > > Hi, > > If I declare a variable and initialize it with an array literal whose > elements are integer literals and nil literals, > the compiler will infer the type Array for that variable:

Re: [swift-users] Improving compilation times?

2017-03-23 Thread Mark Lacey via swift-users
ithin the last couple months so you need to be > using a recent build in order to use this command-line option. Where did the > compiler that you tried it with come from? > > Mark > >> >> Regards, >> Piotr >> >> czw., 23 mar 2017 o 08:54 użytk

Re: [swift-users] Improving compilation times?

2017-03-23 Thread Mark Lacey via swift-users
d to be using a recent build in order to use this command-line option. Where did the compiler that you tried it with come from? Mark > > Regards, > Piotr > > czw., 23 mar 2017 o 08:54 użytkownik Mark Lacey via swift-users > <swift-users@swift.org <mailto:swift-users@swi

Re: [swift-users] Improving compilation times?

2017-03-23 Thread Mark Lacey via swift-users
> 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] Overload Resolution of Binary Operators

2016-11-14 Thread Mark Lacey via swift-users
> On Nov 14, 2016, at 2:05 PM, Toni Suter via swift-users > wrote: > > Hi, > > I would have expected that the following code reports an error, because > of ambiguous function overloads: > > infix operator ***: MultiplicationPrecedence > infix operator +++:

Re: [swift-users] Overload Resolution

2016-10-06 Thread Mark Lacey via swift-users
> On Oct 6, 2016, at 4:53 AM, Toni Suter via swift-users > wrote: > > Hi, > > Does someone know a good explanation / summary of Swift's overload resolution > rules? > After reading https://github.com/apple/swift/blob/master/docs/TypeChecker.rst >

Re: [swift-users] Function overload resolution rules

2016-09-30 Thread Mark Lacey via swift-users
> On Sep 30, 2016, at 5:02 AM, Toni Suter via swift-users > wrote: > > Hi, > > I am trying to get a better understanding of Swift's function overload > resolution rules. > As far as I can tell, if there are multiple candidates for a function call, > Swift favors >

Re: [swift-users] Assertion Failure When Using the swift-DEVELOPMENT-SNAPSHOT-2016-08-04-a Xcode Toolchain

2016-08-04 Thread Mark Lacey via swift-users
> On Aug 4, 2016, at 8:51 PM, Saagar Jha via swift-users > wrote: > > Hello Swift Users, > > This afternoon I updated my Xcode to Xcode 8 beta 4, and tried to compile one > of my previously migrated Swift 3 projects. Along with a couple of renames, > the compiler kept

Re: [swift-users] Redeclaration of guard variable is ignored at top-level

2016-06-17 Thread Mark Lacey via swift-users
> On Jun 16, 2016, at 10:18 PM, Martin R via swift-users > wrote: > > Hi, > > I wonder why the Swift compiler does not complain about the > redeclaration of `number` after the guard-statement in top-level code: > >// main.swift >import Swift > >guard let