<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=""><div><blockquote type="cite" class=""><div class=""><div class="bloop_markdown" style="font-family: Helvetica, Arial; font-size: 13px; 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; background-color: rgb(254, 254, 254);"><p style="margin: 15px 0px;" class="">I was updating some of my libraries where I noticed that the new<span class="Apple-converted-space"> </span><code style="font-family: Menlo, Consolas, 'Liberation Mono', Courier, monospace; font-size: 10pt; border-top-left-radius: 3px; border-top-right-radius: 3px; border-bottom-right-radius: 3px; border-bottom-left-radius: 3px; background-color: rgb(248, 248, 248); color: inherit; border: 1px solid rgb(234, 234, 234); margin: 0px 2px; padding: 0px 5px; word-break: normal; word-wrap: normal; -webkit-margin-before: 0px;" class="">open</code><span class="Apple-converted-space"> </span>access modifier made the<span class="Apple-converted-space"> </span><code style="font-family: Menlo, Consolas, 'Liberation Mono', Courier, monospace; font-size: 10pt; border-top-left-radius: 3px; border-top-right-radius: 3px; border-bottom-right-radius: 3px; border-bottom-left-radius: 3px; background-color: rgb(248, 248, 248); color: inherit; border: 1px solid rgb(234, 234, 234); margin: 0px 2px; padding: 0px 5px; word-break: normal; word-wrap: normal;" class="">public</code><span class="Apple-converted-space"> </span>modifier inconsistent in one way.</p><p style="margin: 15px 0px;" class="">Conformances to protocols is logically the same as inheritances on classes.<span class="Apple-converted-space"> </span></p></div></div></blockquote></div>At least it is very, very similar, and most of the syntax is identical.<div class="">Considering the demand for "sealed" protocols, imho this inconsistency should be addressed as soon as possible.</div><div class=""><br class=""></div><div class="">Afair, the decision for "public as restriction of open" happened quite quickly… I guess simply adding "sealed" would have spared Swift from a huge, breaking change and avoided the protocol-issue as well.</div><div class=""><br class=""></div><div class="">Tino</div></body></html>