<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 Dec 10, 2016, at 5:29 PM, David Sweeris via swift-evolution <<a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div 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;" class=""><blockquote type="cite" class=""><div class=""><br class="Apple-interchange-newline">On Dec 10, 2016, at 4:54 PM, Tommaso Piazza via swift-evolution <<a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class=""><div class="" style="background-color: rgb(255, 255, 255); font-family: HelveticaNeue, 'Helvetica Neue', Helvetica, Arial, 'Lucida Grande', sans-serif; font-size: 16px;"><div dir="ltr" id="yui_3_16_0_ym19_1_1481417388759_3640" class="">Hello,</div><div dir="ltr" id="yui_3_16_0_ym19_1_1481417388759_3640" class=""><br class=""></div><div dir="ltr" id="yui_3_16_0_ym19_1_1481417388759_3640" class="">I have written a small proposal that would allow overloads of operators in structs/classes non only based on the types of the operands but on the return type as well.</div><div dir="ltr" id="yui_3_16_0_ym19_1_1481417388759_3640" class=""><br class=""></div><div dir="ltr" id="yui_3_16_0_ym19_1_1481417388759_3640" class="">Please let me know you thoughts,</div><div dir="ltr" id="yui_3_16_0_ym19_1_1481417388759_3640" class="">/Tommaso</div><div dir="ltr" id="yui_3_16_0_ym19_1_1481417388759_3640" class=""><br class=""></div><div dir="ltr" id="yui_3_16_0_ym19_1_1481417388759_3640" class=""><a href="https://github.com/blender/swift-evolution/blob/proposal/overloads-return-type/NNNN-allow-operator-overloads-in-structs-or-classes-based-on-return-type.md" id="yui_3_16_0_ym19_1_1481417388759_3639" class="">https://github.com/blender/swift-evolution/blob/proposal/overloads-return-type/NNNN-allow-operator-overloads-in-structs-or-classes-based-on-return-type.md</a><br class=""></div></div></div></div></blockquote><br class=""></div><div 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;" class="">That seems like a bug to me… Dunno, maybe it’s intentional and I’m just not aware of the reasoning.</div></div></blockquote><div><br class=""></div>Actually, since the error message correctly parses the code, it probably <i class="">is</i> intentional… I don’t see the problem, myself, but I guess I’d have to know why it’s considered an error before judging whether I think we should remove the restriction.</div><div><br class=""></div>- Dave Sweeris</body></html>