I've thought about how to deal with override in a way that is consistent with the language. Maybe something like this?
// publicly visible but can't be subclassed. public private(subclass) // publicly visible and may be subclasses within the module. The default public internal(subclass) // publicly visible and may be subclasses by all. public public(subclass) We also can not forget how it apples to methods public private(override) public internal(override) public public(override) On Mon, Feb 20, 2017 at 2:12 PM Joanna Carter via swift-evolution < swift-evolution@swift.org> wrote: > > > Le 20 févr. 2017 à 19:18, Dimitri Racordon <dimitri.racor...@unige.ch> > a écrit : > > > > Sorry I pressed the wrong button, and the mail was sent right away. > > I was about to add that I could give it a try, or offer my help. > > Since I still haven't worked out how to submit a proposal, if you know how > to, maybe you should take the lead. > > If you want to contact me offline during the preparation, please feel free > > -- > Joanna Carter > Carter Consulting > _______________________________________________ > swift-evolution mailing list > swift-evolution@swift.org > https://lists.swift.org/mailman/listinfo/swift-evolution >
_______________________________________________ swift-evolution mailing list swift-evolution@swift.org https://lists.swift.org/mailman/listinfo/swift-evolution
