Re: [swift-evolution] [Pitch] Fully eliminate implicit bridging conversions in Swift 3

> On Apr 19, 2016, at 7:28 AM, Greg Parker wrote: > > >> On Apr 18, 2016, at 8:21 PM, Joe Pamer via swift-evolution >> > wrote: >> >> I propose that we fully eliminate implicit bridging conversions in Swift 3.

Re: [swift-evolution] [Pitch] Fully eliminate implicit bridging conversions in Swift 3

What bothers me is that it won't be possible to opt into conversions during imports. I've created a proposal, which solves all related importing problems: https://github.com/Anton3/swift-evolution/blob/shadowing-imported-functions/proposals/-shadowing-imported-functions.md It passed largely

Re: [swift-evolution] [Pitch] Fully eliminate implicit bridging conversions in Swift 3

> On Apr 18, 2016, at 8:21 PM, Joe Pamer via swift-evolution > wrote: > > I propose that we fully eliminate implicit bridging conversions in Swift 3. > This would mean that some users might have to introduce introduce a few more > ‘as’ casts in their code, but we

Re: [swift-evolution] [Pitch] Fully eliminate implicit bridging conversions in Swift 3

+1 from me On Tue, Apr 19, 2016 at 8:42 AM, Haravikk via swift-evolution < swift-evolution@swift.org> wrote: > +1 from me; I’ve been dealing with a lot of conversion and yet it’s still > pretty confusing largely because of the implicit conversions, it also goes > against (pure) Swift’s elegant

Re: [swift-evolution] [Pitch] Fully eliminate implicit bridging conversions in Swift 3

+1 from me; I’ve been dealing with a lot of conversion and yet it’s still pretty confusing largely because of the implicit conversions, it also goes against (pure) Swift’s elegant yet strictly typed checking system. > On 19 Apr 2016, at 04:21, Joe Pamer via swift-evolution >

Re: [swift-evolution] [Pitch] Fully eliminate implicit bridging conversions in Swift 3

I fully support this proposal. IMO we should be moving forward and improve Swift, separate it from ObjC and explicitly bridge when needed. On 19.04.2016 6:21, Joe Pamer via swift-evolution wrote: Hi everyone, Prior to Swift 1.2, conversions between bridged Swift value types and their

Re: [swift-evolution] [Pitch] Fully eliminate implicit bridging conversions in Swift 3

Is it true that some CF APIs, such as these, are still imported as CFString instead of String? https://github.com/apple/swift-3-api-guidelines-review/blob/swift-3/Platforms/OSX/CoreText/CTFontTraits.swift#L2-L9 On Mon, Apr 18, 2016 at 8:21 PM, Joe Pamer via swift-evolution <

[swift-evolution] [Pitch] Fully eliminate implicit bridging conversions in Swift 3

Hi everyone, Prior to Swift 1.2, conversions between bridged Swift value types and their associated Objective-C types could be implicitly inferred in both directions. For example, you could pass an NSString object to a function expecting a String value, and vice versa. In time we found this