Re: [swift-corelibs-dev] non-inherited init

2016-03-20 Thread Philippe Hausler via swift-corelibs-dev
e Hausler via swift-corelibs-dev > Sent by: swift-corelibs-dev-boun...@swift.org > <mailto:swift-corelibs-dev-boun...@swift.org> > Date: 03/17/2016 08:12PM > Cc: Swift corelibs dev <mailto:swift-corelibs-dev@swift.org>> > Subject: Re: [swift-corelibs-dev] non-inhe

Re: [swift-corelibs-dev] non-inherited init

2016-03-19 Thread Pushkar N Kulkarni via swift-corelibs-dev
Sorry for intruding!I have the same question about /*@NSCopying*/  Pushkar N Kulkarni, IBM RuntimesSimplicity is prerequisite for reliability - Edsger W. Dijkstra -swift-corelibs-dev-boun...@swift.org wrote: -To: Daniel Eggert From: Philippe Hausler via swift-corelibs-d

Re: [swift-corelibs-dev] non-inherited init

2016-03-19 Thread Philippe Hausler via swift-corelibs-dev
That is a comment emitted by the importer, unfortunately it is impossible for non objc to mimic that behavior 100% because it is an init method that is constructed from a class method. @interface Foo : NSObject + (Foo *)fooNamed:(NSString *)name; // this is not an inherited init method in that

[swift-corelibs-dev] non-inherited init

2016-03-19 Thread Daniel Eggert via swift-corelibs-dev
There're some initializers (namely in NSURLSession) that have a comment: public /*not inherited*/ init(... What is this “not inherited” comment trying to convey, and how would one go about implementing this in Swift? /Daniel ___ swift-corelibs-dev ma