<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div><blockquote type="cite" class=""><div class="">On Jun 30, 2016, at 1:50 PM, Xiaodi Wu <<a href="mailto:xiaodi.wu@gmail.com" class="">xiaodi.wu@gmail.com</a>> wrote:</div><div class=""><div dir="ltr" class=""><div class="gmail_extra"><div class="gmail_quote">On Thu, Jun 30, 2016 at 3:47 PM, John McCall <span dir="ltr" class=""><<a href="mailto:rjmccall@apple.com" target="_blank" class="">rjmccall@apple.com</a>></span> wrote:<br class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word" class=""><span class=""><div class=""><blockquote type="cite" class=""><div class="">On Jun 30, 2016, at 1:44 PM, Xiaodi Wu <<a href="mailto:xiaodi.wu@gmail.com" target="_blank" class="">xiaodi.wu@gmail.com</a>> wrote:</div><div class=""><div dir="ltr" class=""><div class="gmail_extra"><div class="gmail_quote">On Thu, Jun 30, 2016 at 3:36 PM, John McCall <span dir="ltr" class=""><<a href="mailto:rjmccall@apple.com" target="_blank" class="">rjmccall@apple.com</a>></span> wrote:<br class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word" class=""><div class=""><span class=""><blockquote type="cite" class=""><div class="">On Jun 29, 2016, at 1:33 PM, Xiaodi Wu <<a href="mailto:xiaodi.wu@gmail.com" target="_blank" class="">xiaodi.wu@gmail.com</a>> wrote:</div><div class=""><div dir="ltr" class=""><div class="gmail_extra"><div class="gmail_quote">On Wed, Jun 29, 2016 at 2:54 PM, John McCall via swift-evolution <span dir="ltr" class=""><<a href="mailto:swift-evolution@swift.org" target="_blank" class="">swift-evolution@swift.org</a>></span> wrote:<br class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">> On Jun 29, 2016, at 11:39 AM, Vladimir.S <<a href="mailto:svabox@gmail.com" target="_blank" class="">svabox@gmail.com</a>> wrote:<br class="">
> How about `public(extensible)` ?<br class="">
<br class="">
Hmm. I started to work out an example with these as separate modifiers, and I think I understand the need to combine them in some way.<br class="">
<br class="">
I wonder if just "extensible" would be good enough. It is a term that's used in API descriptions.<br class=""></blockquote><div class=""><br class=""></div><div class="">This particular word is unfortunate because it has nothing to do with an extension, which shares the same etymological root.</div></div></div></div></div></blockquote><div class=""><br class=""></div></span>I agree, but I'm not sure that it's particularly confusing in practice.</div></div></blockquote><div class=""> </div><div class="">Why not just "inheritable"? That is, after all, what we mean, no?</div></div></div></div></div></blockquote><div class=""><br class=""></div></div></span>All class methods are intrinsically inheritable. A non-inheritable method would *require* an override.</div></blockquote><div class=""><br class=""></div><div class="">Sorry, I was more suggesting that word in the context of `public(inheritable)`, provided the default is sealed.</div></div></div></div></div></blockquote><div><br class=""></div></div>The same argument applies: both sealed and unsealed methods are capable of being inherited. And you don't inherit classes, you inherit *from* them.<div class=""><br class=""></div><div class="">If we're going to go along those lines, we should just use public(subclassable) and public(overridable). We can fall back on those if necessary; I would just like to continue looking for better alternatives.<br class=""><div class=""><div class=""><br class=""></div><div class="">John.</div></div></div></body></html>