> Am 19.07.2016 um 04:11 schrieb Jonathan Hull via swift-evolution
> <[email protected] <mailto:[email protected]>>:
>
> Second, I would really like to see the methods match the open-ness or
> final-ity of their enclosing scope by default. Note: I also feel this way
> about access levels, which work this way except for public… I believe they
> should work the same way for public too (while keeping internal as the
> default level for top-level structures).
afaics, I completely agree with your whole message, but this one is worth to be
emphasized:
The effect of "public" should be propagated in the same way as "open"; I don't
think there is any good reason to have two different models for similar
concepts.
I think it would be even better to extend propagation up to module-level, and
let the author decide what access levels are right for him — but that's most
likely way beyond the willingness for compromise.
_______________________________________________
swift-evolution mailing list
[email protected]
https://lists.swift.org/mailman/listinfo/swift-evolution
