[swift-evolution] [Review] SE-0058: Allow Swift types to provide custom Objective-C representations

> On Apr 5, 2016, at 5:57 PM, Kevin Lundberg via swift-evolution < swift-evolution at swift.org> wrote: > > Generally I'm +1 on this, but I do have a concern. It's not made explicit in the proposal, but I presume that this is meant to only be available on Darwin, and not Linux or other platforms

Re: [swift-evolution] [Review] SE-0058: Allow Swift types to provide custom Objective-C representations

On 4/6/2016 1:22 PM, Russ Bishop wrote: > The original intent was to be available on platforms that have an > Objective-C runtime (Darwin only at the moment, I guess in theory > Windows if someone were determined enough). > > > You bring up a good point; there is nothing in the protocol that >

Re: [swift-evolution] [Review] SE-0058: Allow Swift types to provide custom Objective-C representations

on Wed Apr 06 2016, Russ Bishop wrote: > On Apr 5, 2016, at 1:39 PM, Dave Abrahams via swift-evolution > wrote: > > A few thoughts: > > 1. It would have made it easier to evaluate if the proposal had not > talked about

Re: [swift-evolution] [Review] SE-0058: Allow Swift types to provide custom Objective-C representations

> On Apr 5, 2016, at 5:57 PM, Kevin Lundberg via swift-evolution > wrote: > > Generally I'm +1 on this, but I do have a concern. It's not made explicit in > the proposal, but I presume that this is meant to only be available on > Darwin, and not Linux or other

Re: [swift-evolution] [Review] SE-0058: Allow Swift types to provide custom Objective-C representations

(Sorry, sent without finishing a sentence.) >> https://github.com/apple/swift-evolution/blob/master/proposals/0058-objectivecbridgeable.md > >> But then, these *are* intended to be full-width type conversions, >> are they not? Why not these: >> >> init?(_ source: ObjectiveCType) >>

Re: [swift-evolution] [Review] SE-0058: Allow Swift types to provide custom Objective-C representations

on Mon Apr 04 2016, Joe Groff wrote: > Hello Swift community, > > The review of “Allow Swift types to provide custom Objective-C > representations” > begins now and runs through April 11, 2016. The proposal is available here: > >

Re: [swift-evolution] [Review] SE-0058: Allow Swift types to provide custom Objective-C representations

> On Apr 5, 2016, at 11:36 AM, Russ Bishop wrote: > > >> On Apr 5, 2016, at 10:14 AM, Douglas Gregor > > wrote: >>> Suppose there is also a subclass (say, ObjCMutableFizzer), and we have this Objective-C API:

Re: [swift-evolution] [Review] SE-0058: Allow Swift types to provide custom Objective-C representations

> On Apr 5, 2016, at 10:14 AM, Douglas Gregor wrote: >> >>> Suppose there is also a subclass (say, ObjCMutableFizzer), and we have this >>> Objective-C API: >>> >>> ObjCMutableFizzer* mutableFizzer; >>> >>> Which of these represents how it is imported? >>> >>> var

Re: [swift-evolution] [Review] SE-0058: Allow Swift types to provide custom Objective-C representations

> On Apr 4, 2016, at 9:54 PM, Russ Bishop via swift-evolution > wrote: > >> >> On Apr 4, 2016, at 9:22 PM, Brent Royal-Gordon via swift-evolution >> wrote: >> >>> >>>

Re: [swift-evolution] [Review] SE-0058: Allow Swift types to provide custom Objective-C representations

> On Apr 4, 2016, at 9:22 PM, Brent Royal-Gordon via swift-evolution > wrote: > >> >> https://github.com/apple/swift-evolution/blob/master/proposals/0058-objectivecbridgeable.md > > There are a number of things I'm not really clear on. > > * * * > > Consider

Re: [swift-evolution] [Review] SE-0058: Allow Swift types to provide custom Objective-C representations

> > https://github.com/apple/swift-evolution/blob/master/proposals/0058-objectivecbridgeable.md There are a number of things I'm not really clear on. * * * Consider this Objective-C API: ObjCFizzer* myFizzer; Which of these represents how it is imported? var myFizzer:

Re: [swift-evolution] [Review] SE-0058: Allow Swift types to provide custom Objective-C representations

• What is your evaluation of the proposal? Good idea, it gets rid of compiler magic • Is the problem being addressed significant enough to warrant a change to Swift? Yes, plenty of mixed projects. Plenty of Cocoa libraries that could be improved with a Swift API. • Does this proposal fit well

[swift-evolution] [Review] SE-0058: Allow Swift types to provide custom Objective-C representations

Hello Swift community, The review of “Allow Swift types to provide custom Objective-C representations” begins now and runs through April 11, 2016. The proposal is available here: https://github.com/apple/swift-evolution/blob/master/proposals/0058-objectivecbridgeable.md Reviews are an