<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="">I sincerely apologize for the lack of professionalism in my response. I will try to maintain higher standards in future communication.</div><div class=""><br class=""></div><div class="">Best regards. -- E</div><br class=""><div><blockquote type="cite" class=""><div class="">On Feb 8, 2016, at 9:41 PM, Vanderlei Martinelli <<a href="mailto:vmartinelli@alecrim.com" class="">vmartinelli@alecrim.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class="">@EricaSadun I’d like to say that many of us are not native English speakers. I had to find what is the meaning of “gimme” and “dunno”. And it is a good thing, so I can learn more English words and slangs. But at the same time sometimes I read these messages in a place where it is not possible to consult dictionaries or when I just do not have time to do this.<div class=""><br class=""></div><div class="">OK... Let’s explain the words:</div><div class=""><br class=""></div><div class="">gimme. noun. <span class="" style="font-family: -apple-system; font-size: 13px;">a thing that is very easy to perform or obtain, <span class="">especially</span> in a game or sport<span class="">:</span><span class=""></span></span><span class="" style="font-family: -apple-system; font-size: 13px;"><span class="" style="font-style:italic"> the kick would hardly be a gimme in that wind</span></span><br class=""><div class=""><br class=""></div><div class="">dunno. contraction. <span style="font-size: 13px; font-family: -apple-system;" class="">(I) do not know</span><span class="" style="font-size: 13px; font-family: -apple-system;">. origin </span><span class="" style="font-size: 13px; font-family: -apple-system;"><span class=""><span class="">mid</span> 19<span class="">th</span> cent.</span></span><span style="font-size: 13px; font-family: -apple-system;" class="">: </span><span style="font-size: 13px; font-family: -apple-system;" class="">representing</span><span style="font-size: 13px; font-family: -apple-system;" class=""> an informal </span><span style="font-size: 13px; font-family: -apple-system;" class="">pronunciation</span><span class="" style="font-size: 13px; font-family: -apple-system;">.</span></div><div class=""><br class=""></div></div><div class="">;-)<br class=""></div><div class=""><br class=""></div><div class="">Dunno, but the more we use internationally known words may be a gimme to track the subject that is Swift evolution.<br class=""></div><div class=""><br class=""></div></div><div class="gmail_extra"><br class=""><div class="gmail_quote">On Tue, Feb 9, 2016 at 1:47 AM, Erica Sadun via swift-evolution <span dir="ltr" class=""><<a href="mailto:swift-evolution@swift.org" target="_blank" class="">swift-evolution@swift.org</a>></span> wrote:<br class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=""><br class="">
> On Feb 8, 2016, at 8:32 PM, Joe Groff via swift-evolution <<a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a>> wrote:<br class="">
><br class="">
><br class="">
>> On Feb 8, 2016, at 7:25 PM, Joe Groff via swift-evolution <<a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a>> wrote:<br class="">
>><br class="">
>> Javier Soto brought up a case where his ReactiveCocoa code silently did the wrong thing by implicitly discarding the result of a closure:<br class="">
>><br class="">
>> <a href="https://twitter.com/Javi/status/695680700033306624" rel="noreferrer" target="_blank" class="">https://twitter.com/Javi/status/695680700033306624</a><br class="">
>><br class="">
>> Since it sounds like we plan on making `@warn_unused_result` the default, it seems natural to also warn when a closure has its result type converted away to Void. If there's one 'return' statement, we could dive into the return expression to decide whether to warn based on the function whose result is getting ignored.<br class="">
><br class="">
> There's another axis of intent in whether the closure was written with an explicit return or not. `{ foo($0) }` is ambivalent to whether it intends to propagate the value returned by `foo` or not, whereas `{ return foo($0) }` is explicitly trying to do so. IMO we have a stronger case to warn if the `return` is explicit in the closure body.<br class="">
<br class="">
<br class="">
</span>if foo is -> Void, it's a gimme.<br class="">
if foo is -> T with @warn_unused_result, it's a gimme<br class="">
if foo is -> T without @warn_unused_result, dunno<br class="">
<span class="HOEnZb"><font color="#888888" class=""><br class="">
-- E<br class="">
</font></span><div class="HOEnZb"><div class="h5"><br class="">
_______________________________________________<br class="">
swift-evolution mailing list<br class="">
<a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a><br class="">
<a href="https://lists.swift.org/mailman/listinfo/swift-evolution" rel="noreferrer" target="_blank" class="">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br class="">
</div></div></blockquote></div><br class=""></div>
</div></blockquote></div><br class=""></body></html>