<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 class="">Proposal</div><div class=""><a href="https://github.com/apple/swift-evolution/blob/master/proposals/0186-remove-ownership-keyword-support-in-protocols.md" class="">https://github.com/apple/swift-evolution/blob/master/proposals/0186-remove-ownership-keyword-support-in-protocols.md</a></div><div class=""><br class=""></div><div class=""><blockquote type="cite" class=""><div class="" style="word-wrap: break-word; -webkit-nbsp-mode: space;"><div class=""><div class=""><div class="">* What is your evaluation of the proposal?</div><div class=""><br class=""></div></div></div></div></blockquote><div class=""><br class=""></div><div class="">A tentative +1</div><div class=""><br class=""></div><blockquote type="cite" class=""><div class="" style="word-wrap: break-word; -webkit-nbsp-mode: space;"><div class=""><div class=""><div class="">* Is the problem being addressed significant enough to warrant a change to Swift?</div></div></div></div></blockquote><div class=""><br class=""></div><div class="">BUT…</div><div class=""><br class=""></div><div class="">It does convey some information. Without looking at the definition of A, I know it is a class or a class-bound protocol.</div><div class=""><br class=""></div><div class="">As currently used, the protocol is saying that it is not necessarily required to maintain the lifetime A, but that doesn’t mean that it cannot. I think of this in the same way a protocol declares var x: Int { get } and can satisfy this with let x = 10.</div><div class=""><br class=""></div><div class="">That said I don’t know if this is an important use case. I have never used it.</div><br class=""><blockquote type="cite" class=""><div class="" style="word-wrap: break-word; -webkit-nbsp-mode: space;"><div class=""><div class=""><div class="">* Does this proposal fit well with the feel and direction of Swift?</div><div class=""><br class=""></div></div></div></div></blockquote><div class=""><br class=""></div><div class="">Sticking to the path of least surprise is probably a good idea. Another path would to be to add a bevy of uncheckable annotations such as complexity requirements, etc. That doesn’t seem to be the path we want to go so it fits well with that.</div><div class=""><br class=""></div><br class=""><blockquote type="cite" class=""><div class="" style="word-wrap: break-word; -webkit-nbsp-mode: space;"><div class=""><div class=""><div class="">* If you have used other languages or libraries with a similar feature, how do you feel that this proposal compares to those?</div></div></div></div></blockquote><div class=""><br class=""></div><div class="">No</div><div class=""><br class=""></div><blockquote type="cite" class=""><div class="" style="word-wrap: break-word; -webkit-nbsp-mode: space;"><div class=""><div class=""><div class=""><br class=""></div><div class="">* How much effort did you put into your review? A glance, a quick reading, or an in-depth study?</div></div></div></div></blockquote></div><div class=""><div class="" style="word-wrap: break-word; -webkit-nbsp-mode: space;"><div class=""><div class=""><div class=""><br class=""></div></div></div></div></div><div class="">quick reading</div><div class=""><br class=""></div></body></html>