<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="">Sorry for the late reply,<div class=""><br class=""></div><div class=""><b class="">Ted: </b></div><div class=""><br class=""></div><div class="">A JIRA? I know that’s issue tracking, where can I get one of those?</div><div class=""><br class=""></div><div class="">This is my first foray into the swift open source mailing lists, so I apologize for my certain level of novice.</div><div class=""><br class=""><div class="">
<div class=""><div style="margin: 0px; color: rgb(144, 144, 144);" class=""><b class="">_________________</b></div><div style="margin: 0px; color: rgb(144, 144, 144);" class=""><b class="">Sean Alling</b></div><div style="margin: 0px; color: rgb(144, 144, 144);" class="">Mechanical Engineer</div><div style="margin: 0px; color: rgb(144, 144, 144);" class="">703 . 843 . 4808</div><div style="margin: 0px; font-size: 13px; color: rgb(144, 144, 144);" class=""><a href="mailto:allings@vcu.edu" class="">allings@icloud.com</a></div></div>
</div>
<br class=""><div><blockquote type="cite" class=""><div class="">On 9 Jul , 2016, at 00:58, Ted kremenek <<a href="mailto:kremenek@apple.com" class="">kremenek@apple.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class=""><br class=""><br class=""><blockquote type="cite" class="">On Jul 6, 2016, at 8:24 PM, Douglas Gregor via swift-dev <<a href="mailto:swift-dev@swift.org" class="">swift-dev@swift.org</a>> wrote:<br class=""><br class=""><br class=""><blockquote type="cite" class="">On Jun 25, 2016, at 1:19 PM, Sean Alling via swift-dev <<a href="mailto:swift-dev@swift.org" class="">swift-dev@swift.org</a>> wrote:<br class=""><br class="">Hi everyone,<br class=""><br class="">I’m suggesting a change to the compiler that returns an error when an object 'does not conform to protocol’ to nest sub-errors that’ll list what properties and methods the object hasn’t implemented.<br class=""><br class="">I’m using the idea of a nested error so that the exceptions thrown will be grouped when shown. That was each doesn’t create a new error, racking up the error count, but rather just showing the developer the things he/she needs to implement.<br class=""></blockquote><br class="">I would *love* for us to have errors with Fix-Its that put in stub declarations for what you need to implement to conform to the protocol. I don’t think you should use sub-errors, though, because the structure doesn’t always come across well in IDEs. Rather, I’d suggest emitting one error per missing requirement, with a Fix-It that adds the proper declaration into the type/extension that declared conformance, and a note pointing to the requirement itself.<br class=""><br class=""> - Doug<br class=""></blockquote><br class="">Do we have a JIRA issue for this idea?<br class=""><br class=""><blockquote type="cite" class=""><br class="">_______________________________________________<br class="">swift-dev mailing list<br class=""><a href="mailto:swift-dev@swift.org" class="">swift-dev@swift.org</a><br class="">https://lists.swift.org/mailman/listinfo/swift-dev<br class=""></blockquote></div></div></blockquote></div><br class=""></div></body></html>