<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></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 Jan 28, 2016, at 11:35 PM, Fabian Ehrentraud <<a href="mailto:Fabian.Ehrentraud@willhaben.at" class="">Fabian.Ehrentraud@willhaben.at</a>> wrote:</div><br class="Apple-interchange-newline"><div class="">
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252" class="">
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">
Too bad to hear the PR was rejected by the Core Team. I'm sad about it, but the reasoning sounds valid.
<div class="">
<div class=""><br class="">
</div>
<div class="">
<blockquote type="cite" class="">Solution #2 is asking for a warning, which is outside the scope of the Swift evolution process.<br class="">
</blockquote>
<div class=""><br class="">
</div>
<div class="">I was a bit baffled by this information at first, but it's true that the goals of the Swift evolution process state that. I'm not sure though, how to propose additional warnings, when I only have the idea and no code to provide as a PR? The Contributing
guidelines do not clarify that case. Should I just create a ticket at <a href="http://bugs.swift.org/" class="">bugs.swift.org</a>?</div>
</div></div></div></div></blockquote><br class=""></div><div>A warning is a feature of the compiler, so filing a feature request at <a href="http://bugs.swift.org" class="">bugs.swift.org</a> is appropriate. </div><div><br class=""></div><div><span class="Apple-tab-span" style="white-space:pre"> </span>- Doug</div><div><br class=""></div><br class=""></body></html>