Re: [swift-corelibs-dev] Coercion problems on Linux

2016-09-08 Thread Philippe Hausler via swift-corelibs-dev
>From a technical perspective it is not impossible to do however as of current >reference type to structural type bridging is conflated with the objective c >runtime being present (specifically present on Darwin targets). Personally I >think we need a better answer than what we have today but I

Re: [swift-corelibs-dev] Coercion problems on Linux

2016-09-08 Thread Pushkar N Kulkarni via swift-corelibs-dev
Hi Philippe, Thanks for your response! I have one more question.>> In general it is because we don't have bridging on Linux.Will we have it in future? Pardon my ignorance. Pushkar N Kulkarni, IBM RuntimesSimplicity is prerequisite for reliability - Edsger W. Dijkstra -phaus...@apple.com wrote:

Re: [swift-corelibs-dev] Coercion problems on Linux

2016-09-08 Thread Philippe Hausler via swift-corelibs-dev
That particular issue we could plaster over with generics. In general it is because we don't have bridging on Linux. Sent from my iPhone > On Sep 8, 2016, at 8:36 AM, Pushkar N Kulkarni wrote: > > Hi Tony/Philippe, > > There've been a few bug reports related to the coercion problems between

[swift-corelibs-dev] Coercion problems on Linux

2016-09-08 Thread Pushkar N Kulkarni via swift-corelibs-dev
Hi Tony/Philippe, There've been a few bug reports related to the coercion problems between Swift and Foundation types on Linux. For example this one: https://bugs.swift.org/browse/SR-2477 (Double/Int don't coerce with NSNumber on Linux). Is there any general approach you'd suggest to work around th