<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">
<br class="">
<div>
<blockquote type="cite" class="">
<div class="">On 21 Feb 2017, at 09:09, Joanna Carter <<a href="mailto:joanna@carterconsulting.org.uk" class="">joanna@carterconsulting.org.uk</a>> wrote:</div>
<br class="Apple-interchange-newline">
<div class=""><span style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">The
reality of the Swift world is that it is no longer just classes that are extensible (by subclassing) but, also, extensions that can be written against any type.</span></div>
</blockquote>
</div>
<br class="">
<div class="">I totally agree with that.</div>
<div class=""><br class="">
</div>
<div class="">It’s actually something that bothers me with the open access modifier. It introduces an asymmetry on the language and emphasis on classes, while I think Swift do its best not to.</div>
<div class=""><br class="">
</div>
</body>
</html>