[swift-users] minimum deployment target

Hello, I have some code that is used in both a project with minimum deployment target 10.9 and a project with minimum deployment target 10.11. If I check for availability of API’s on the 10.9 project I get warnings on the 10.11 project saying these checks are unnecessary. Can I conditionalize

Re: [swift-users] minimum deployment target

Maybe you should ask this question in https://forums.developer.apple.com/welcome Zhaoxin On Mon, Nov 14, 2016 at 6:26 PM, J.E. Schotsman via swift-users < swift-users@swift.org> wrote: > Hello, > > I have some code that is used in both a project with minimum deployment > target 10.9 and a

[swift-users] A place where community meets: Swift news aggregator proposal

Hi Swift enthusiasts! My name is Dmitri Pavlutin. I'm a Swift enthusiast too! I blog about Swift and JavaScript languages at https://rainsoft.io. When I publish articles about Swift, one drawback (compared to JavaScript situation) is the limited number of places where I can share new articles.

[swift-users] LLDB can't access the value of an associated type variable

Hello, I have an issue with a project, I was trying to inspect the value of a constant of type [GeneType], this type is defined as an associatedtype of a protocol, so there is no explicit type for it, just a constraint to be Hashable : > protocol GAStandardGenomeRepresentable { > >

Re: [swift-users] Overload Resolution of Binary Operators

I seem to remember that while it is possible to define, the compiler will yield an error if you try to use the functions (“cannot resolve”). Regards, Rien Site: http://balancingrock.nl Blog: http://swiftrien.blogspot.com Github: http://github.com/Swiftrien Project: http://swiftfire.nl > On

Re: [swift-users] Optimising Set comparisons

Many thanks to Tim for suggesting isSubset, which I had somehow missed while browsing the documentation. To answer Dave's questions: unfortunately the Set comparisons aren't an ideal candidate for asynchronous work. The comparisons take place as part of a CSS-like styling phase, whereby a number

Re: [swift-users] Decimal imported as NSDecimal not NSDecimalNumber in Swift 3 to Objective C

Thanks for that follow up, I’m still a little confused at why one direction works and the other does not, but I’m getting there. I’ve found another issue I’ll bug report, but it’s along the same lines and wanted to run it by this thread. If I have an NSDecimalNumber, in Swift, and perform math

[swift-users] Overload Resolution of Binary Operators

Hi, I would have expected that the following code reports an error, because of ambiguous function overloads: infix operator ***: MultiplicationPrecedence infix operator +++: AdditionPrecedence func ***(x: Int, y: Int) -> String { print("f1") return "" } func ***(x: Int, y: Int)

Re: [swift-users] Overload Resolution of Binary Operators

> On Nov 14, 2016, at 16:05, 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 of Binary Operators

> 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] Decimal imported as NSDecimal not NSDecimalNumber in Swift 3 to Objective C

Literals in Swift do not inherently have a type (at least conceptually). They are simply literals. The compiler will interpret them as whatever ExpressibleBy_Literal type is required to make the expression sensible. There are default types which literals will become if no type information is

Re: [swift-users] Reflection in Swift 3?

Thanks, David. That's interesting as a thought exercise, but doesn't really get me away from having switch statements. I'll probably end up just "slightly polluting" my classes by adding extension methods to create the appropriate auxiliary classes. Sure wish Swift supported optional methods